 |
|
| If you can't view the Datasheet, Please click here to try to view without PDF Reader . |
|
|
|
| If you can't view the Datasheet, Please click here to try to view without PDF Reader . |
|
|
| Datasheet File OCR Text: |
| features ? high performance, low power avr ? 8-bit microcontroller ? advanced risc architecture ? 120 powerful instructions ? most single clock cycle execution ? 32 x 8 general purpose working registers ? fully static operation ? non-volatile program and data memories ? 2/4/8k bytes of in-system programmable program memory flash ? endurance: 10,000 write/erase cycles ? 128/256/512 bytes in-system pr ogrammable eeprom ? endurance: 100,000 write/erase cycles ? 128/256/512 bytes internal sram ? programming lock for self-program ming flash program and eeprom data security ? peripheral features ? 8-bit timer/counter with pr escaler and two pwm channels ? 8-bit high speed timer/counte r with separate prescaler ? 2 high frequency pwm outputs with separate output compare registers ? programmable dead time generator ? usi ? universal seri al interface with start condition detector ? 10-bit adc ? 4 single ended channels ? 2 differential adc channel pairs with programmable gain (1x, 20x) ? temperature measurement ? programmable watchdog timer with separate on-chip oscillator ? on-chip analog comparator ? special microcontroller features ? debugwire on-chip debug system ? in-system programmable via spi port ? external and internal interrupt sources ? low power idle, adc noise reduction, and power-down modes ? enhanced power-on reset circuit ? programmable brown-out detection circuit ? internal calibrated oscillator ? i/o and packages ? six programmable i/o lines ? 8-pin pdip, 8-pin soic, 20-pad qfn/mlf, and 8-pin tssop (only attiny45/v) ? operating voltage ? 1.8 - 5.5v for attiny25v/45v/85v ? 2.7 - 5.5v for attiny25/45/85 ? speed grade ? attiny25v/45v/85v: 0 ? 4 mhz @ 1.8 - 5.5v, 0 - 10 mhz @ 2.7 - 5.5v ? attiny25/45/85: 0 ? 10 mhz @ 2.7 - 5.5v, 0 - 20 mhz @ 4.5 - 5.5v ? industrial temperature range ? low power consumption ? active mode: ? 1 mhz, 1.8v: 300 a ? power-down mode: ? 0.1 a at 1.8v 8-bit microcontroller with 2/4/8k bytes in-system programmable flash attiny25/v attiny45/v attiny85/v rev. 2586n?avr?04/11
2 2586n?avr?04/11 attiny25/45/85 1. pin configurations figure 1-1. pinout attiny25/45/85 1.1 pin descriptions 1.1.1 vcc supply voltage. 1.1.2 gnd ground. 1.1.3 port b (pb5:pb0) port b is a 6-bit bi-directional i/o port with inte rnal pull-up resistors (selected for each bit). the port b output buffers have symmetrical drive characteristics with both high sink and source capability. as inputs, port b pi ns that are externally pulled low will source current if the pull-up 1 2 3 4 8 7 6 5 (pcint5/reset/adc0/dw) pb5 (pcint3/xtal1/clki/oc1b/adc3) pb3 (pcint4/xtal2/clko/oc1b/adc2) pb4 gnd vcc pb2 (sck/usck/scl/adc1/t0/int0/pcint2) pb1 (miso/do/ain1/oc0b/oc1a/pcint1) pb0 (mosi/di/sda/ain0/oc0a/oc1a/aref/pcint0) pdip/soic/tssop 1 2 3 4 5 qfn/mlf 15 14 13 12 11 20 19 18 17 16 6 7 8 9 10 dnc dnc gnd dnc dnc dnc dnc dnc dnc dnc note: bottom pad should be soldered to ground. dnc: do not connect note: tssop only for attiny45/v (pcint5/reset/adc0/dw) pb5 (pcint3/xtal1/clki/oc1b/adc3) pb3 dnc dnc (pcint4/xtal2/clko/oc1b/adc2) pb4 vcc pb2 (sck/usck/scl/adc1/t0/int0/pcint2) dnc pb1 (miso/do/ain1/oc0b/oc1a/pcint1) pb0 (mosi/di/sda/ain0/oc0a/oc1a/aref/pcint0) 3 2586n?avr?04/11 attiny25/45/85 resistors are activated. the port b pins are tri-stated when a reset condition becomes active, even if the clock is not running. port b also serves the functions of various s pecial features of the attiny25/45/85 as listed in ?alternate functions of port b? on page 62 . on attiny25, the programmable i/o ports pb3 and pb4 (pins 2 and 3) are exchanged in attiny15 compatibility mode for supporting the backward compatibility with attiny15. 1.1.4 reset reset input. a low level on this pin for longer than the minimum pulse length will generate a reset, even if the clock is not running and prov ided the reset pin has not been disabled. the min- imum pulse length is given in table 21-4 on page 170 . shorter pulses are not guaranteed to generate a reset. the reset pin can also be used as a (weak) i/o pin. 4 2586n?avr?04/11 attiny25/45/85 2. overview the attiny25/45/85 is a low-power cmos 8-bit microcontroller based on the avr enhanced risc architecture. by executing powerful instructio ns in a single clock cycle, the attiny25/45/85 achieves throughputs approaching 1 mips per mhz allowing the system designer to optimize power consumption versus processing speed. 2.1 block diagram figure 2-1. block diagram the avr core combines a rich instruction set with 32 general purpose working registers. all 32 registers are directly connected to the arithmetic logic unit (alu), allowing two independent program counter calibrated internal oscillator watchdog timer stack pointer program flash sram mcu control register general purpose registers instruction register timer/ counter0 serial universal interface timer/ counter1 instruction decoder data dir. reg.port b data register port b programming logic timing and control mcu status register status register alu port b drivers pb[0:5] vcc gnd control lines 8-bit databus z adc / analog comparator interrupt unit data eeprom oscillators y x reset 5 2586n?avr?04/11 attiny25/45/85 registers to be accessed in one single instruction executed in one clock cycle. the resulting architecture is more code efficient while achiev ing throughputs up to ten times faster than con- ventional cisc microcontrollers. the attiny25/45/85 provides the following featur es: 2/4/8k bytes of in-system programmable flash, 128/256/512 bytes eeprom, 128/256/256 bytes sram, 6 general purpose i/o lines, 32 general purpose working registers, one 8-bit timer/counter with compare modes, one 8-bit high speed timer/counter, universal serial interface, internal and external interrupts, a 4-channel, 10-bit adc, a programmable watc hdog timer with in ternal oscillato r, and three so ftware select- able power saving modes. idle mode stops the cpu while allowing the sram, timer/counter, adc, analog comparator, and interrupt system to continue functioning. power-down mode saves the register contents, disabling all chip functions until the next interrupt or hardware reset. adc noise reduction mode stops the cpu and all i/o modules except adc, to minimize switching noise during adc conversions. the device is manufactured using atmel?s high density non-volatile memory technology. the on-chip isp flash allows the program memory to be re-programmed in-system through an spi serial interface, by a conventional non-volatile memory programmer or by an on-chip boot code running on the avr core. the attiny25/45/85 avr is supported with a full suite of program and system development tools including: c compilers, macro as semblers, program debugger/simulators and evaluation kits. 6 2586n?avr?04/11 attiny25/45/85 3. about 3.1 resources a comprehensive set of development tools, app lication notes and datasheets are available for download on http:// www.atmel.com/avr. 3.2 code examples this documentation contains simple code examples that briefly show how to use various parts of the device. these code examples assume that the part specific header file is included before compilation. be aware that not all c compiler vendors include bit definitions in the header files and interrupt handling in c is compiler dependent. please confirm with the c compiler documen- tation for more details. for i/o registers located in the extended i/o map, ?in?, ?out?, ?sbis?, ?sbic?, ?cbi?, and ?sbi? instructions must be replaced with instructions that allow access to extended i/o. typically, this means ?lds? and ?sts? combined with ?sbrs?, ?s brc?, ?sbr?, and ?cbr?. note that not all avr devices include an extended i/o map. 3.3 capacitive touch sensing atmel qtouch library provides a simple to use solution for touch sensitive interfaces on atmel avr microcontrollers. the qtouch library includes support for qtouch ? and qmatrix ? acquisi- tion methods. touch sensing is easily added to any application by linking the qtouch library and using the application programming interface (api) of the library to define the touch channels and sensors. the application then calls the api to retrieve channel information and determine the state of the touch sensor. the qtouch library is free and can be downloaded from the atmel website. for more informa- tion and details of implementation, refer to the qtouch library user guide ? also available from the atmel website. 3.4 data retention reliability qualification results show that the pr ojected data retention failure rate is much less than 1 ppm over 20 years at 85c or 100 years at 25c. 7 2586n?avr?04/11 attiny25/45/85 4. avr cpu core 4.1 introduction this section discusses the avr core architecture in general. the main function of the cpu core is to ensure correct program execution. the cpu must therefore be able to access memories, perform calculations, control peripherals, and handle interrupts. 4.2 architectural overview figure 4-1. block diagram of the avr architecture in order to maximize performance and parallelism, the avr uses a harvard architecture ? with separate memories and buses for program and data. instructions in the program memory are executed with a single level pipelining. while one instruction is being executed, the next instruc- tion is pre-fetched from the program memory. this concept enables instructions to be executed in every clock cycle. the program memory is in-system reprogrammable flash memory. flash program memory instruction register instruction decoder program counter control lines 32 x 8 general purpose registrers alu status and control i/o lines eeprom data bus 8-bit data sram direct addressing indirect addressing interrupt unit watchdog timer analog comparator i/o module 2 i/o module1 i/o module n 8 2586n?avr?04/11 attiny25/45/85 the fast-access register file contains 32 x 8-bit general purpose working registers with a single clock cycle access time. this allows single-cycle ar ithmetic logic unit (alu ) operation. in a typ- ical alu operation, two operands are output from the register file, the operation is executed, and the result is stored back in the register file ? in one clock cycle. six of the 32 registers can be used as three 16-b it indirect address register pointers for data space addressing ? enabling efficient address calculations. one of the these address pointers can also be used as an address pointer for look up tables in flash program memory. these added function registers are the 16-bit x-, y-, and z-register, described later in this section. the alu supports arithmetic and logic operations between registers or between a constant and a register. single register operations can also be executed in the alu. after an arithmetic opera- tion, the status register is updated to reflect information about the result of the operation. program flow is provided by conditional and uncon ditional jump and call instructions, able to directly address the whole address space. most avr instructions have a single 16-bit word for- mat, but there are also 32-bit instructions. during interrupts and subroutine calls, the return address program counter (pc) is stored on the stack. the stack is effectively allocated in the general data sram, and consequently the stack size is only limited by the to tal sram size and the usage of the sram. all user programs must initialize the sp in the reset routine (before subroutines or interrupts are executed). the stack pointer (sp) is read/write accessible in the i/o space. the data sram can easily be accessed through the five different addressing modes supported in the avr architecture. the memory spaces in the avr architecture are all linear and regular memory maps. a flexible interrupt module has its control r egisters in the i/o space with an additional global interrupt enable bit in the status register. all interrupts have a separate interrupt vector in the interrupt vector table. the interrupts have priority in accordance with their interrupt vector posi- tion. the lower the interrupt vector address, the higher the priority. the i/o memory space contains 64 addresses for cpu peripheral functi ons as control regis- ters, spi, and other i/o functions. the i/o memory can be accessed directly, or as the data space locations following those of the register file, 0x20 - 0x5f. 4.3 alu ? arithm etic logic unit the high-performance avr alu operates in dire ct connection with all the 32 general purpose working registers. within a single clock cycle, arithmetic operations between general purpose registers or between a register and an immediate are executed. the alu operations are divided into three main categories ? arithmetic, logical, and bit-functions. some implementations of the architecture also provide a powerful multiplier supporting both signed/unsigned multiplication and fractional format. see the ?instruction set? section for a detailed description. 4.4 status register the status register contains information about the result of the most recently executed arithme- tic instruction. this information can be used for altering program flow in order to perform conditional operations. note that the status register is updated after all alu operations, as specified in the instruction set reference. this will in many cases remove the need for using the dedicated compare instructions, resulting in faster and more compact code. the status register is not automatically stored when entering an interrupt routine and restored when returning from an interrupt. this must be handled by software. 9 2586n?avr?04/11 attiny25/45/85 4.4.1 sreg ? avr status register the avr status register ? sreg ? is defined as: ? bit 7 ? i: global interrupt enable the global interrupt enable bit must be set for th e interrupts to be enabled. the individual inter- rupt enable control is then performed in separate control registers. if the global interrupt enable register is cleared, none of the interrupts are enabled independent of the individual interrupt enable settings. the i-bit is cleared by hardware after an interrupt has occurred, and is set by the reti instruction to enable subsequent interrupts. the i-bit can also be set and cleared by the application with the sei and cli instructions, as described in the instruction set reference. ? bit 6 ? t: bit copy storage the bit copy instructions bld (bit load) and bst (b it store) use the t-bit as source or desti- nation for the operated bit. a bit from a register in the register file can be copied into t by the bst instruction, and a bit in t can be copied into a bit in a register in the register file by the bld instruction. ? bit 5 ? h: half carry flag the half carry flag h indicates a half carry in some arithmetic operation s. half carry is useful in bcd arithmetic. see the ?instruction set description? for detailed information. ? bit 4 ? s: sign bit, s = n v the s-bit is always an exclusive or between the negative flag n and the two?s complement overflow flag v. see the ?instruction set description? for detailed information. ? bit 3 ? v: two?s complement overflow flag the two?s complement overflow flag v suppor ts two?s complement arithmetics. see the ?instruction set description? for detailed information. ? bit 2 ? n: negative flag the negative flag n indicates a negative result in an arithmetic or logic operation. see the ?instruction set description? for detailed information. ? bit 1 ? z: zero flag the zero flag z indicates a zero result in an arithmetic or logic operation. see the ?instruction set description? for detailed information. ? bit 0 ? c: carry flag the carry flag c indicates a carry in an arithmetic or logic operation. see the ?instruction set description? for de tailed information. bit 76543210 0x3f i t h s v n z c sreg read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value00000000 10 2586n?avr?04/11 attiny25/45/85 4.5 general purpose register file the register file is optimized for the avr enhanc ed risc instruction set. in order to achieve the required performance and flex ibility, the following in put/output schemes ar e supported by the register file: ? one 8-bit output operand and one 8-bit result input ? two 8-bit output operands and one 8-bit result input ? two 8-bit output operands and one 16-bit result input ? one 16-bit output operand and one 16-bit result input figure 4-2 shows the structure of the 32 general purpose working registers in the cpu. figure 4-2. avr cpu general purpose working registers most of the instructions operating on the register file have direct access to all registers, and most of them are single cycle instructions. as shown in figure 4-2 , each register is also assigned a data memory address, mapping them directly into the first 32 locations of the user data space. although not being physically imple- mented as sram locations, this memory organization provides great flexibility in access of the registers, as the x-, y- and z-pointer registers can be set to index any register in the file. 4.5.1 the x-register, y-register, and z-register the registers r26..r31 have some added functions to their general purpose usage. these reg- isters are 16-bit address pointers for indirect addressing of the data space. the three indirect address registers x, y, and z are defined as described in figure 4-3 . 7 0 addr. r0 0x00 r1 0x01 r2 0x02 ? r13 0x0d general r14 0x0e purpose r15 0x0f working r16 0x10 registers r17 0x11 ? r26 0x1a x-register low byte r27 0x1b x-register high byte r28 0x1c y-register low byte r29 0x1d y-register high byte r30 0x1e z-register low byte r31 0x1f z-register high byte 11 2586n?avr?04/11 attiny25/45/85 figure 4-3. the x-, y-, and z-registers in the different addressing modes these address registers have functions as fixed displacement, automatic increment, and automatic decrement (see the instruction set reference for details). 4.6 stack pointer the stack is mainly used for storing temporary data, for storing local variables and for storing return addresses after interrupts and subroutine calls. the stack pointer register always points to the top of the stack. note that the stack is implemented as growing from higher memory loca- tions to lower memory locations. this implies that a stack push command decreases the stack pointer. the stack pointer points to the data sram stack area where the subroutine and interrupt stacks are located. this stack space in the data sram must be defined by the program before any subroutine calls are executed or interrupts are enabled. the stack pointer must be set to point above 0x60. the stack pointer is decrement ed by one when data is pushed onto the stack with the push instruction, and it is decremented by two when the return address is pushed onto the stack with subroutine call or interrupt. the stack pointer is incremented by one when data is popped from the stack with the pop instruction, and it is incremented by two when data is popped from the stack with return from subroutine ret or return from interrupt reti. the avr stack pointer is implemented as two 8- bit registers in the i/o space. the number of bits actually used is implementation dependent. note that the data space in some implementa- tions of the avr architecture is so small that only spl is needed. in this case, the sph register will not be present. 4.6.1 sph and spl ? stack pointer register 15 xh xl 0 x-register 707 0 r27 (0x1b) r26 (0x1a) 15 yh yl 0 y-register 707 0 r29 (0x1d) r28 (0x1c) 15 zh zl 0 z-register 7070 r31 (0x1f) r30 (0x1e) bit 151413121110 9 8 0x3e sp15 sp14 sp13 sp12 sp11 sp10 sp9 sp8 sph 0x3d sp7 sp6 sp5 sp4 sp3 sp2 sp1 sp0 spl 76543210 read/write r/w r/w r/w r/w r/w r/w r/w r/w read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value ramend ramend ramend ramend ramend ramend ramend ramend initial value ramend ramend ramend ramend ramend ramend ramend ramend 12 2586n?avr?04/11 attiny25/45/85 4.7 instruction execution timing this section describes the general access timi ng concepts for instruction execution. the avr cpu is driven by the cpu clock clk cpu , directly generated from the selected clock source for the chip. no internal clo ck division is used. figure 4-4 shows the parallel instruction fetches and instruction executions enabled by the har- vard architecture and the fast access register file concept. this is the basic pipelining concept to obtain up to 1 mips per mhz with the corr esponding unique results for functions per cost, functions per clocks, and functions per power-unit. figure 4-4. the parallel instruction fetches and instruction executions figure 4-5 shows the internal timing concept for the register file. in a single clock cycle an alu operation using two register operands is executed, and the result is stored back to the destina- tion register. figure 4-5. single cycle alu operation 4.8 reset and inte rrupt handling the avr provides several different interrupt sources. these interrupts and the separate reset vector each have a separate program vector in the program memory space. all interrupts are assigned individual enable bits which must be written logic one together with the global interrupt enable bit in the status register in order to enable the interrupt. the lowest addresses in the program memory space are by default defined as the reset and interrupt vectors. the complete list of vectors is shown in ?interrupts? on page 50 . the list also determines the priority levels of the different interrupts. the lower the address the higher is the priority level. reset has the highest priority, and next is int0 ? the external interrupt request 0. clk 1st instruction fetch 1st instruction execute 2nd instruction fetch 2nd instruction execute 3rd instruction fetch 3rd instruction execute 4th instruction fetch t1 t2 t3 t4 cpu total execution time register operands fetch alu operation execute result write back t1 t2 t3 t4 clk cpu 13 2586n?avr?04/11 attiny25/45/85 when an interrupt occurs, the global interrupt enable i-bit is cleared and all interrupts are dis- abled. the user software can write logic one to the i-bit to enable nested interrupts. all enabled interrupts can then interrupt the current interrupt routine. the i-bit is automatically set when a return from interrupt instruction ? reti ? is executed. there are basically two types of interrupts. the fi rst type is triggered by an event that sets the interrupt flag. for these interrupts, the program counter is vectored to the actual interrupt vec- tor in order to execute the interrupt handling routine, and hardware clears the corresponding interrupt flag. interrupt flags can also be cleared by writing a logic one to the flag bit position(s) to be cleared. if an interrupt condition occurs while the corresponding interrupt enable bit is cleared, the interrupt fl ag will be set and remember ed until the interrupt is enabled, or the flag is cleared by software. similarly, if one or more interrupt conditions occur while the global interrupt enable bit is clea red, the corres ponding interrupt fl ag(s) will be set and remembered until the global interrupt enable bit is set, and will then be exec uted by order of priority. the second type of interrupts will trigger as long as the interrupt condition is present. these interrupts do not necessarily have interrupt flags. if the interrupt condition disappears before the interrupt is enabled, the in terrupt will not be triggered. when the avr exits from an inte rrupt, it will always retu rn to the main pr ogram and execute one more instruction before any pending interrupt is served. note that the status register is not automatica lly stored when entering an interrupt routine, nor restored when returning from an interrupt routine. this must be handled by software. when using the cli instruction to disable interrupts, the interrup ts will be immediately disabled. no interrupt will be executed af ter the cli instruction, even if it occurs simultaneously with the cli instruction. the following example shows how this can be used to avoid interrupts during the timed eeprom write sequence. assembly code example in r16, sreg ; store sreg value cli ; disable interrupts during timed sequence sbi eecr, eempe ; start eeprom write sbi eecr, eepe out sreg, r16 ; restore sreg value (i-bit) c code example char csreg; csreg = sreg; /* store sreg value */ /* disable interrupts during timed sequence */ _cli(); eecr |= (1< 15 2586n?avr?04/11 attiny25/45/85 5. avr memories this section describes the different memories in the attiny25/45/85. the avr architecture has two main memory spaces, the data memory and the program memory space. in addition, the attiny25/45/85 feat ures an eeprom memory for data storag e. all three memory spaces are lin- ear and regular. 5.1 in-system re-programmable flash program memory the attiny25/45/85 contains 2/4/8k bytes on -chip in-system reprogrammable flash memory for program storage. since all avr instructions ar e 16 or 32 bits wide, the flash is organized as 1024/2048/4096 x 16. the flash memory has an endurance of at least 10,000 write/erase cycles. the attiny25/45/85 program counter (pc) is 10/11/12 bits wide, thus addressing the 1024/2048/4096 program memory locations. ?memory programming? on page 151 contains a detailed description on flash data serial downloading using the spi pins. constant tables can be allocated within the entire program memory address space (see the lpm ? load program memory instruction description). timing diagrams for instruction fetch and execution are presented in ?instruction execution tim- ing? on page 12 . figure 5-1. program memory map 5.2 sram data memory figure 5-2 shows how the attiny25/45/85 sram memory is organized. the lower 224/352/607 data memory locations address both the register file, the i/o memory and the internal data sram. the first 32 locations address the register file, the next 64 loca- tions the standard i/o memory, and the last 128/256/512 locations address the internal data sram. the five different addressing modes for the data memory cover: direct, indirect with displace- ment, indirect, indirect with pre-decrement, and indirect with post-increment. in the register file, registers r26 to r31 feature the indirect addressing pointer registers. the direct addressing reaches the entire data space. the indirect with displacement mode reaches 63 address locations from the base address given by the y- or z-register. 0x0000 0x03ff/0x07ff/0x0fff program memory 16 2586n?avr?04/11 attiny25/45/85 when using register indirect addressing modes with automatic pre-decrement and post-incre- ment, the address registers x, y, and z are decremented or incremented. the 32 general purpose working registers, 64 i/o registers, and the 128/256/512 bytes of inter- nal data sram in the attiny25/45/85 are all ac cessible through all these addressing modes. the register file is described in ?general purpose register file? on page 10 . figure 5-2. data memory map 5.2.1 data memory access times this section describes the general access timi ng concepts for internal memory access. the internal data sram access is performed in two clk cpu cycles as described in figure 5-3 . figure 5-3. on-chip data sram access cycles 5.3 eeprom data memory the attiny25/45/85 contains 128/256/512 bytes of data eeprom memory. it is organized as a separate data space, in which single bytes can be read and written. the eeprom has an endurance of at least 100,000 write/erase cycles. the access between the eeprom and the cpu is described in the following, specif ying the eeprom address registers, the eeprom data register, and the eeprom c ontrol register. for details see ?serial downloading? on page 155 . 5.3.1 eeprom read/write access the eeprom access registers are accessible in the i/o space. 32 registers 64 i/o registers internal sram (128/256/512 x 8) 0x0000 - 0x001f 0x0020 - 0x005f 0x0df/0x015f/0x025f 0x0060 data memory clk wr rd data data address address valid t1 t2 t3 compute address read write cpu memory access instruction next instruction 17 2586n?avr?04/11 attiny25/45/85 the write access times for the eeprom are given in table 5-1 on page 21 . a self-timing func- tion, however, lets the user software detect when the next byte can be written. if the user code contains instructions that write the eeprom, so me precautions must be taken. in heavily fil- tered power supplies, v cc is likely to rise or fall slo wly on power-up/down. this causes the device for some period of time to run at a voltage lower than specified as minimum for the clock frequency used. see ?preventing eeprom corruption? on page 19 for details on how to avoid problems in these situations. in order to prevent unintentional eeprom writes, a specific write procedure must be followed. refer to ?atomic byte programming? on page 17 and ?split byte programming? on page 17 for details on this. when the eeprom is read, the cpu is halted for fo ur clock cycles before the next in struction is executed. when the eeprom is written, the cp u is halted for two clock cycles before the next instruction is executed. 5.3.2 atomic byte programming using atomic byte programming is the simplest mode. when writing a by te to the eeprom, the user must write the address into the eear regi ster and data into ee dr register. if the eepmn bits are zero, writing eepe (within four cycles af ter eempe is written) will trigger the erase/write operation. both the erase and write cycle are done in one operation and the total programming time is given in table 5-1 on page 21 . the eepe bit remains set until the erase and write opera- tions are completed. while the device is busy with programming, it is not possible to do any other eeprom operations. 5.3.3 split byte programming it is possible to split the erase and write cycle in two different operations. this may be useful if the system requires short access time for some limited period of ti me (typically if the power sup- ply voltage falls). in order to take advantage of this method, it is required that the locations to be written have been erased before the write operation. but since the erase and write operations are split, it is possible to do the erase operations when the system allows doing time-critical operations (typically after power-up). 5.3.4 erase to erase a byte, the address must be written to eear. if the eepmn bits are 0b01, writing the eepe (within four cycles after eempe is written) will trigger the erase operation only (program- ming time is given in table 5-1 on page 21 ). the eepe bit remains se t until the erase operation completes. while the device is busy programming, it is not possible to do any other eeprom operations. 5.3.5 write to write a location, the user must write the address into eear and the data into eedr. if the eepmn bits are 0b10, writing the eepe (within f our cycles after eempe is written) will trigger the write operation only (programming time is given in table 5-1 on page 21 ). the eepe bit remains set until the write operation completes. if the location to be written has not been erased before write, the data that is stored must be considered as lost. while the device is busy with programming, it is not possible to do any ot her eeprom operations. the calibrated oscillator is used to time the eeprom accesses. make sure the oscillator fre- quency is within the requirements described in ?osccal ? oscillator ca libration register? on page 32 . 18 2586n?avr?04/11 attiny25/45/85 the following code examples show one assembly and one c function for erase, write, or atomic write of the eeprom. the examples assume that interrupts are controlled (e.g., by disabling interrupts globally) so that no interrupts will occur during ex ecution of th ese functions. assembly code example eeprom_write: ; wait for completion of previous write sbic eecr,eepe rjmp eeprom_write ; set programming mode ldi r16, (0< 21 2586n?avr?04/11 attiny25/45/85 5.5.3 eecr ? eeprom control register ? bit 7 ? res: reserved bit this bit is reserved for future use and will always read as 0 in attiny25/45/85. for compatibility with future avr devices, always write this bit to zero. after reading, mask out this bit. ? bit 6 ? res: reserved bit this bit is reserved in the attiny 25/45/85 and will always read as zero. ? bits 5:4 ? eepm[1:0]: eepr om programming mode bits the eeprom programming mode bits setting defines which programming action that will be triggered when writing eepe. it is possible to program data in one atomic operation (erase the old value and program the new value) or to split the erase and write operations in two different operations. the programming times for the different modes are shown in table 5-1 . while eepe is set, any write to eepmn will be ignored. du ring reset, the eepmn bits will be reset to 0b00 unless the eeprom is busy programming. ? bit 3 ? eerie: eeprom ready interrupt enable writing eerie to one enab les the eeprom ready interrupt if th e i-bit in sreg is set. writing eerie to zero disables the interrupt. the eep rom ready interrupt generates a constant inter- rupt when non-volatile memory is ready for programming. ? bit 2 ? eempe: eeprom master program enable the eempe bit determines whether writing eepe to o ne will have effect or not. when eempe is set, setting eepe within four cl ock cycles will program the eeprom at the selected address. if eempe is zero, setting eepe will have no effect. when eempe has been written to one by software, hardware clears the bit to zero after four clock cycles. ? bit 1 ? eepe: eeprom program enable the eeprom program enable signal eepe is th e programming enable signal to the eeprom. when eepe is written, the eeprom will be pr ogrammed according to the eepmn bits setting. the eempe bit must be written to one before a logical one is written to eepe, otherwise no eeprom write takes place. when the write a ccess time has elapsed, the eepe bit is cleared by hardware. when eepe has been set, the cpu is halted for two cycles before the next instruction is executed. bit 76543210 0x1c ? ? eepm1 eepm0 eerie eempe eepe eere eecr read/write r r r/w r/w r/w r/w r/w r/w initial value 0 0 x x 0 0 x 0 table 5-1. eeprom mode bits eepm1 eepm0 programming time operation 0 0 3.4 ms erase and write in one operation (atomic operation) 0 1 1.8 ms erase only 1 0 1.8 ms write only 1 1 ? reserved for future use 22 2586n?avr?04/11 attiny25/45/85 ? bit 0 ? eere: eeprom read enable the eeprom read enable signal ? eere ? is t he read strobe to the eeprom. when the cor- rect address is set up in the eear register, the eere bit must be written to one to trigger the eeprom read. the eeprom read access takes one instruction, and th e requested data is available immediately. when t he eeprom is read, the cpu is ha lted for four cycles before the next instruction is executed. th e user should poll the eepe bit be fore starting the read opera- tion. if a write operation is in progress, it is neither possible to read the eeprom, nor to change the eear register. 23 2586n?avr?04/11 attiny25/45/85 6. system clock and clock options 6.1 clock systems and their distribution figure 6-1 presents the principal clock systems in the avr and their distribution. all of the clocks need not be active at a given time. in order to reduce power consumption, the clocks to modules not being used can be halted by using different sleep modes, as described in ?power manage- ment and sleep modes? on page 35 . the clock systems are detailed below. figure 6-1. clock distribution 6.1.1 cpu clock ? clk cpu the cpu clock is routed to parts of the system concerned with operation of the avr core. examples of such modules are the general pur pose register file, the status register and the data memory holding the stack pointer. halting the cpu clock inhibits the core from performing general operations and calculations. 6.1.2 i/o clock ? clk i/o the i/o clock is used by the majority of the i/o modules, like timer/counter. the i/o clock is also used by the external interrupt module, but note that some external interrupts are detected by asynchronous logic, allowing such interrupts to be detected even if the i/o clock is halted. 6.1.3 flash clock ? clk flash the flash clock controls operation of the flash in terface. the flash clock is usually active simul- taneously with the cpu clock. general i/o modules cpu core ram clk i/o avr clock control unit clk cpu flash and eeprom clk flash source clock watchdog timer watchdog oscillator reset logic clock multiplexer watchdog clock calibrated rc oscillator calibrated rc oscillator external clock adc clk adc crystal oscillator low-frequency crystal oscillator system clock prescaler pll oscillator clk pck clk pck 24 2586n?avr?04/11 attiny25/45/85 6.1.4 adc clock ? clk adc the adc is provided with a dedicated clock domain. this allows halting the cpu and i/o clocks in order to reduce noise generated by digital circuitry. this gives more accurate adc conversion results. 6.1.5 internal pll for fast peripheral clock generation - clk pck the internal pll in attiny25/45/85 generates a clock frequency that is 8x multiplied from a source input. by default, the pll uses the output of the internal, 8.0 mhz rc oscillator as source. alternatively, if bit lsm of pllcsr is set the pll will use the ou tput of the rc oscillator divided by two. thus the output of the pll, the fa st peripheral clock is 64 mhz. the fast periph- eral clock, or a clock prescaled from that, can be selected as the clock source for timer/counter1 or as a system clock. see figure 6-2 . the frequency of the fast peripheral clock is divided by two when lsm of pllcsr is set, resulting in a clock frequency of 32 mhz. note, that lsm can not be set if pll clk is used as system clock. figure 6-2. pck clocking system. the pll is locked on the rc oscillator and adju sting the rc oscillator via osccal register will adjust the fast peripheral clock at the same time. however, even if the rc oscillator is taken to a higher frequency than 8 mhz, the fast peripheral clock frequency saturates at 85 mhz (worst case) and remains oscillating at the maximum frequency. it should be noted that the pll in this case is not locked any longer with the rc oscillator clock. therefore, it is recommended not to take the osccal adjustments to a higher frequency than 8 mhz in order to keep the pll in the correct operating range. the internal pll is enabled when: ? the plle bit in the register pllcsr is set. ? the cksel fuse is pr ogrammed to ?0001?. ? the cksel fuse is pr ogrammed to ?0011?. the pllcsr bit plock is set when pll is locked. both internal rc oscillator and pll are switched off in power down and stand-by sleep modes. 6.1.6 internal pll in attiny15 compatibility mode since attiny25/45/85 is a migration device for attiny15 users there is an attiny15 compatibility mode for backward compatibility. the attiny15 co mpatibility mode is selected by programming the cksel fuses to ?0011?. 1/2 8 mhz lsm 8.0 mhz oscillator pll 8x cksel[3:0] plle osccal 4 mhz 1/4 lock detector prescaler clkps[3:0] system clock plock pck oscillators xtal1 xtal2 64 / 32 mhz 8 mhz 16 mhz 25 2586n?avr?04/11 attiny25/45/85 in the attiny15 compatibility mode the frequency of the internal rc oscillator is calibrated down to 6.4 mhz and the multiplication factor of the pll is set to 4x. see figure 6-3 . with these adjustments the clocking system is attiny15-comp atible and the resulting fast peripheral clock has a frequency of 25.6 mhz (same as in attiny15). figure 6-3. pck clocking system in attiny15 compatibility mode. note that low speed mode is not impl emented in attiny15 compatibility mode. 6.2 clock sources the device has the following clock source options, selectable by flash fuse bits as shown below. the clock from the selected source is input to the avr clock generator, and routed to the appropriate modules. note: 1. for all fuses ?1? means unprogrammed while ?0? means programmed. 2. the device is shipped with this option selected. 3. this will select attiny15 compatibility mode, wher e system clock is divided by four, resulting in a 1.6 mhz clock frequency. for more inormation, see ?calibrated inte rnal oscillator? on page 27 . the various choices for each clocking option is given in the following sections. when the cpu wakes up from power-down, the selected clock source is used to time the start-up, ensuring sta- ble oscillator operation before instruction execution starts. when the cpu starts from reset, there is an additional delay allowing the power to reach a stable level before commencing nor- 1/2 1.6 mhz 6.4 mhz o s cillator pll 8 x plle o s ccal 3 .2 mhz lock detector s y s tem clock plock pck 25.6 mhz 1/4 table 6-1. device clocking options select device clocking option cksel[3:0] (1) external clock (see page 26 ) 0000 high frequency pll clock (see page 26 ) 0001 calibrated internal oscillator (see page 27 ) 0010 (2) calibrated internal oscillator (see page 27 ) 0011 (3) internal 128 khz oscillator (see page 29 ) 0100 low-frequency crystal oscillator (see page 29 ) 0110 crystal oscillator / ceramic resonator (see page 30 ) 1000 ? 1111 reserved 0101, 0111 26 2586n?avr?04/11 attiny25/45/85 mal operation. the watchdog osc illator is used for timi ng this real-time part of the start-up time. the number of wdt oscillator cycles us ed for each time-out is shown in table 6-2 . 6.2.1 external clock to drive the device from an external cloc k source, clki should be driven as shown in figure 6- 4 . to run the device on an ex ternal clock, the cksel fuses must be progra mmed to ?00?. figure 6-4. external clock drive configuration when this clock source is sele cted, start-up times are determined by the sut fuses as shown in table 6-3 . when applying an external clock, it is required to avoid sudden changes in the applied clock fre- quency to ensure stable operation of the mcu. a variation in frequency of more than 2% from one clock cycle to the next can lead to unpredictable behavior. it is required to en sure that the mcu is kept in reset during such changes in the clock frequency. note that the system clock prescaler can be used to implement run-time changes of the internal clock frequency while still ensuri ng stable operation. refer to ?system clock prescaler? on page 31 for details. 6.2.2 high frequency pll clock there is an internal pll that provides nominally 64 mhz clock rate locked to the rc oscillator for the use of the peripheral timer/counter1 and for the system clock source. when selected as table 6-2. number of watchdog oscillator cycles typ time-out number of cycles 4 ms 512 64 ms 8k (8,192) table 6-3. start-up times for the external clock selection sut[1:0] start-up time from power-down additional delay from reset recommended usage 00 6 ck 14ck bod enabled 01 6 ck 14ck + 4 ms fast rising power 10 6 ck 14ck + 64 ms slowly rising power 11 reserved external clock signal clki gnd 27 2586n?avr?04/11 attiny25/45/85 a system clock source, by programming the cksel fuses to ?0001?, it is divided by four like shown in table 6-4 . when this clock source is selected, start-up times are determined by the sut fuses as shown in table 6-5 . 6.2.3 calibrated internal oscillator by default, the internal rc os cillator provides an approximat e 8.0 mhz clock. though voltage and temperature dependent, this clock can be ve ry accurately calibrated by the user. see ?cali- brated internal rc oscilla tor accuracy? on page 169 and ?internal oscillator speed? on page 197 for more details. the device is shipped with the ckdiv8 fuse programmed. see ?system clock prescaler? on page 31 for more details. this clock may be selected as the system clock by programming the cksel fuses as shown in table 6-6 on page 28 . if selected, it will operate with no external components. during reset, hardware loads the pre-programmed calibration value into the osccal register and thereby automatically calibrates the rc oscillator. the a ccuracy of this calibration is shown as factory calibration in table 21-2 on page 169 . by changing the osccal register from sw, see ?osccal ? oscillator ca libration register? on page 32 , it is possible to get a higher calibration accuracy than by using the factory calibration. the accuracy of this calibration is shown as user calibration in table 21-2 on page 169 . when this oscillator is used as the chip clock, the watchdog oscillator will still be used for the watchdog timer and for the reset time-out. for more information on the pre-programmed cali- bration value, see the section ?calibration bytes? on page 154 . the internal oscillator can also be set to provide a 6.4 mhz clock by writing cksel fuses to ?0011?, as shown in table 6-6 below. this setting is reffere d to as attiny15 compatibility mode and is intended to provide a calibrated clock source at 6.4 mhz, as in attiny15. in attiny15 compatibility mode the pll uses the internal oscillator running at 6.4 mhz to generate a 25.6 mhz peripheral clock sign al for timer/counter1 (see ?8-bit timer/counter1 in attiny15 table 6-4. high frequency pll clock operating modes cksel[3:0] nominal frequency 0001 16 mhz table 6-5. start-up times for the high frequency pll clock sut[1:0] start-up time from power down additional delay from power-on reset (v cc = 5.0v) recommended usage 00 14ck + 1k (1024) ck + 4 ms 4 ms bod enabled 01 14ck + 16k (16384) ck + 4 ms 4 ms fast rising power 10 14ck + 1k (1024) ck + 64 ms 4 ms slowly rising power 11 14ck + 16k (16384) ck + 64 ms 4 ms slowly rising power 28 2586n?avr?04/11 attiny25/45/85 mode? on page 98 ). note that in this mode of operation the 6.4 mhz clock signal is always divided by four, providing a 1.6 mhz system clock. note: 1. the device is shipped with this option selected. 2. this setting will sele ct attiny15 compatibility mode, wher e system clock is divided by four, resulting in a 1.6 mhz clock frequency. when the calibrated 8 mhz internal oscillator is selected as clock source the start-up times are determined by the sut fuses as shown in table 6-7 below. note: 1. if the rstdisbl fuse is pr ogrammed, this start-up time will be increased to 14ck + 4 ms to ensure programming mode can be entered. 2. the device is shipped with this option selected. in attiny15 compatibility mode start-up times are determined by sut fuses as shown in table 6-8 below. note: 1. if the rstdisbl fuse is pr ogrammed, this start-up time will be increased to 14ck + 4 ms to ensure programming mode can be entered. in summary, more informatio n on attiny15 compatibility mo de can be found in sections ?port b (pb5:pb0)? on page 2 , ?internal pll in attiny15 compatibility mode? on page 24 , ?8-bit timer/counter1 in attiny15 mode? on page 98 , ?limitations of debugwire? on page 144 , ?cali- bration bytes? on page 154 and in table ?clock prescaler select? on page 34 . table 6-6. internal calibrated rc o scillator operating modes cksel[3:0] nominal frequency 0010 (1) 8.0 mhz 0011 (2) 6.4 mhz table 6-7. start-up times for internal calibrated rc oscillator clock sut[1:0] start-up time from power-down additional delay from reset (v cc = 5.0v) recommended usage 00 6 ck 14ck (1) bod enabled 01 6 ck 14ck + 4 ms fast rising power 10 (2) 6 ck 14ck + 64 ms slowly rising power 11 reserved table 6-8. start-up times for internal calibrated rc oscillator clock (i n attiny15 mode) sut[1:0] start-up time from power-down additional delay from reset (v cc = 5.0v) recommended usage 00 6 ck 14ck + 64 ms 01 6 ck 14ck + 64 ms 10 6 ck 14ck + 4 ms 11 1 ck 14ck (1) 29 2586n?avr?04/11 attiny25/45/85 6.2.4 internal 128 khz oscillator the 128 khz internal oscillator is a low power oscillator providing a clock of 128 khz. the fre- quency is nominal at 3v and 25 c. this clock may be select as the system clock by programming the cksel fuses to ?0100?. when this clock source is sele cted, start-up times are determined by the sut fuses as shown in table 6-9 . note: 1. if the rstdisbl fuse is pr ogrammed, this start-up time will be increased to 14ck + 4 ms to ensure programming mode can be entered. 6.2.5 low-frequency crystal oscillator to use a 32.768 khz watch crystal as the clock source for the device, the low-frequency crystal oscillator must be selected by setting cksel fu ses to ?0110?. the crystal should be connected as shown in figure 6-5 . to find suitable load capacitance for a 32.768 khz crysal, please consult the manufacturer?s datasheet. when this oscillator is selected, start-up ti mes are determined by t he sut fuses as shown in table 6-10 . note: 1. these options should be used only if fr equency stability at star t-up is not important. the low-frequency crystal oscillator provides an internal load capacitance, see table 6-11 at each tosc pin. table 6-9. start-up times for the 128 khz internal oscillator sut[1:0] start-up time from power-down additional delay from reset recommended usage 00 6 ck 14ck (1) bod enabled 01 6 ck 14ck + 4 ms fast rising power 10 6 ck 14ck + 64 ms slowly rising power 11 reserved table 6-10. start-up times for the lo w frequency crystal oscillator clock selection sut[1:0] start-up time from power down additional delay from reset (v cc = 5.0v) recommended usage 00 1k (1024) ck (1) 4 ms fast rising power or bod enabled 01 1k (1024) ck (1) 64 ms slowly rising power 10 32k (32768) ck 64 ms stable frequency at start-up 11 reserved table 6-11. capacitance of low-frequency crystal oscillator device 32 khz osc. type cap (xtal1/tosc1) cap (xtal2/tosc2) attiny25/45/85 system osc. 16 pf 6 pf 30 2586n?avr?04/11 attiny25/45/85 6.2.6 crystal oscillator / ceramic resonator xtal1 and xtal2 are input and output, respectively, of an inverting amplifier which can be con- figured for use as an on-chip oscillator, as shown in figure 6-5 . either a quartz crystal or a ceramic resonator may be used. figure 6-5. crystal oscillator connections c1 and c2 should always be equal for both crystals and resonators. the optimal value of the capacitors depends on the crystal or resonator in use, the amount of stray capacitance, and the electromagnetic noise of the environment. some initial guidelines for choosing capacitors for use with crystals are given in table 6-12 below. for ceramic resonators, the capacitor values given by the manufacturer should be used. notes: 1. this option should not be used with crystals, only with ceramic resonators. the oscillator can operate in three different mo des, each optimized for a specific frequency range. the op erating mode is selected by t he fuses cksel[3:1] as shown in table 6-12 . the cksel0 fuse together with the sut[1:0] fuses select the start-up times as shown in table 6-13 . table 6-12. crystal oscillator operating modes cksel[3:1] frequency range (mhz) recommended range for capacitors c1 and c2 for use with crystals (pf) 100 (1) 0.4 - 0.9 ? 101 0.9 - 3.0 12 - 22 110 3.0 - 8.0 12 - 22 111 8.0 - 12 - 22 table 6-13. start-up times for the crysta l oscillator clock selection cksel0 sut[1:0] start-up time from power-down additional delay from reset recommended usage 0 00 258 ck (1) 14ck + 4 ms ceramic resonator, fast rising power 0 01 258 ck (1) 14ck + 64 ms ceramic resonator, slowly rising power 0 10 1k (1024) ck (2) 14ck ceramic resonator, bod enabled xtal2 xtal1 gnd c2 c1 31 2586n?avr?04/11 attiny25/45/85 notes: 1. these options should only be used when not operating close to the maximum frequency of the device, and only if frequency stability at start- up is not important for the application. these options are not suitable for crystals. 2. these options are intended for use with cerami c resonators and will ensure frequency stability at start-up. they can also be used with crystal s when not operating close to the maximum fre- quency of the device, and if frequency stability at start-up is not important for the application. 6.2.7 default clock source the device is shipped with cksel = ?0010?, sut = ?10?, and ckdiv8 programmed. the default clock source setting is therefor e the internal rc oscillator running at 8 mhz with longest start-up time and an initial system clock prescaling of 8, resulting in 1.0 mhz system clock. this default setting ensures that all users can make their desired clock source setting using an in-system or high-voltage programmer. 6.3 system clock prescaler the attiny25/45/85 system clock can be divided by setting the ?clkpr ? clock prescale regis- ter? on page 33 . this feature can be used to decrease power consumption when the requirement for processing power is low. this can be used with all clock source options, and it will affect the clock frequency of the cp u and all synchronou s peripherals. clk i/o , clk adc , clk cpu , and clk flash are divided by a factor as shown in table 6-15 on page 34 . 6.3.1 switching time when switching between prescaler settings, the system clock prescaler ensures that no glitches occur in the clock system and that no intermediate frequency is higher than neither the clock frequency corresponding to the previous setting, nor the clock frequency corresponding to the new setting. the ripple counter that implements the prescaler runs at the frequency of the undivided clock, which may be faster than the cpu?s clock frequency. hence, it is not possible to determine the state of the prescaler ? even if it were readable, and the exact time it takes to switch from one clock division to another cannot be exactly predicted. from the time the clkps values ar e written, it takes between t1 + t2 and t1 + 2*t2 before the new clock frequency is active. in this interval, 2 active clock edges are produced. here, t1 is the previous clock period, and t2 is the period corresponding to the new prescaler setting. 0 11 1k (1024)ck (2) 14ck + 4 ms ceramic resonator, fast rising power 1 00 1k (1024)ck (2) 14ck + 64 ms ceramic resonator, slowly rising power 1 01 16k (16384) ck 14ck crystal oscillator, bod enabled 1 10 16k (16384) ck 14ck + 4 ms crystal oscillator, fast rising power 1 11 16k (16384) ck 14ck + 64 ms crystal oscillator, slowly rising power table 6-13. start-up times for the crystal osc illator clock select ion (continued) cksel0 sut[1:0] start-up time from power-down additional delay from reset recommended usage 32 2586n?avr?04/11 attiny25/45/85 6.4 clock output buffer the device can output the system clock on the clko pin (when not used as xtal2 pin). to enable the output, the ckout fuse has to be programmed. this mode is suitable when the chip clock is used to drive other circuits on the syst em. note that the clock will not be output during reset and that the normal operat ion of the i/o pin will be over ridden when the fuse is pro- grammed. internal rc oscillato r, wdt oscillator, pll, and external clock (clki) can be selected when the clock is output on clko. cryst al oscillators (xtal1, xtal2) can not be used for clock output on clko. if the system clock presca ler is used, it is the divided system clock that is output. 6.5 register description 6.5.1 osccal ? oscillato r calibration register ? bits 7:0 ? cal[7:0]: oscillator calibration value the oscillator calibration register is used to trim the calibrated internal rc oscillator to remove process variations from the oscillator frequency. a pre-programmed calibration value is automatically written to this register during chip reset, giving the factory calibrated frequency as specified in table 21-2 on page 169 . the application software can write this register to change the oscillator frequency. the os cillator can be calibrated to frequencies as specified in table 21- 2 on page 169 . calibration outside that range is not guaranteed. note that this o scillator is used to time eeprom and flash write accesses , and these write times will be affected accordingly. if the eeprom or flash are writ ten, do not calibrate to more than 8.8 mhz. other wise, the eeprom or flash write may fail. the cal7 bit determines the range of operation for the oscillator. setting this bit to 0 gives the lowest frequency range, setting this bit to 1 gives the highest frequency range. the two fre- quency ranges are overlapping, in other words a setting of osccal = 0x7f gives a higher frequency than osccal = 0x80. the cal[6:0] bits are used to tune the frequency within the selected range. a setting of 0x00 gives the lowest frequency in that range, and a setting of 0x7f gives the highest frequency in the range. to ensure stable operation of the mcu the calibration value should be changed in small. a vari- ation in frequency of more than 2% from one cycle to the next can lead to unpredicatble behavior. changes in osccal should not exceed 0x20 for each calibration. it is required to ensure that the mcu is kept in reset during such changes in the clock frequency bit 76543210 0x31 cal7 cal6 cal5 cal4 cal3 cal2 cal1 cal0 osccal read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value device specific calibration value table 6-14. internal rc oscillator frequency range osccal value typical lowest frequency with respect to nominal frequency typical highest frequency with respect to nominal frequency 0x00 50% 100% 0x3f 75% 150% 0x7f 100% 200% 33 2586n?avr?04/11 attiny25/45/85 6.5.2 clkpr ? clock prescale register ? bit 7 ? clkpce: clock prescaler change enable the clkpce bit must be written to logic one to enab le change of the clkps bits. the clkpce bit is only updated when the other bits in clkpr are simultaniosly written to zero. clkpce is cleared by hardware four cycles af ter it is written or when the clkps bits are written. rewriting the clkpce bit within this time-out period does neither extend the time-out period, nor clear the clkpce bit. ? bits 6:4 ? res: reserved bits these bits are reserved bits in the attiny25/45/85 and will always read as zero. ? bits 3:0 ? clkps[3:0]: clock prescaler select bits 3 - 0 these bits define the division factor between the selected clock source and the internal system clock. these bits can be written run-time to vary the clock frequency to suit the application requirements. as the divider divides the master clock input to the mcu, the speed of all synchro- nous peripherals is reduced when a division fact or is used. the division factors are given in table 6-15 . to avoid unintentional changes of clock frequency, a special write procedure must be followed to change the clkps bits: 1. write the clock prescaler change enable (clkpce) bit to one and all other bits in clkpr to zero. 2. within four cycles, write the desired valu e to clkps while writing a zero to clkpce. interrupts must be disabled when changing prescaler setting to make sure the write procedure is not interrupted. the ckdiv8 fuse determines the initial value of the clkps bits. if ckdiv8 is unprogrammed, the clkps bits will be reset to ?0000?. if ckdiv8 is programmed, clkps bits are reset to ?0011?, giving a division factor of eight at star t up. this feature should be used if the selected clock source has a higher frequency than the maximum frequency of the device at the present operating conditions. note that any value can be written to the clkps bits regardless of the ckdiv8 fuse setting. the application software must ensure that a sufficient division factor is chosen if the selcted clock source has a highe r frequency than the maximum frequency of the bit 76543210 0x26 clkpce ? ? ? clkps3 clkps2 clkps1 clkps0 clkpr read/write r/w r r r r/w r/w r/w r/w initial value 0 0 0 0 see bit description 34 2586n?avr?04/11 attiny25/45/85 device at the present operating conditions. the device is shipped with the ckdiv8 fuse programmed. note: the prescaler is disabled in attiny15 compatibility mode and neither writing to clkpr, nor pro- gramming the ckdiv8 fuse has any effect on th e system clock (which will always be 1.6 mhz). table 6-15. clock prescaler select clkps3 clkps2 clkps1 clkps0 clock division factor 0000 1 0001 2 0010 4 0011 8 0100 16 0101 32 0110 64 0111 128 1000 256 1001 reserved 1010 reserved 1011 reserved 1100 reserved 1101 reserved 1110 reserved 1111 reserved 35 2586n?avr?04/11 attiny25/45/85 7. power management and sleep modes the high performance and industry leading code efficiency makes the avr microcontrollers an ideal choise for low power applications. in addition, sleep modes enable the application to shut down unused modules in the mcu, thereby saving power. the avr provides various sleep modes allowing the user to tailor the power consumption to the application?s requirements. 7.1 sleep modes figure 6-1 on page 23 presents the different clock systems and their distribution in attiny25/45/85. the figure is helpful in selecting an appropriate sleep mode. table 7-1 shows the different sleep modes and their wake up sources. note: 1. for int0, only level interrupt. to enter any of the three sleep modes, the se bit in mcucr must be written to logic one and a sleep instruction must be execut ed. the sm[1:0] bits in the mcucr register select which sleep mode (idle, adc noise reduction or powe r-down) will be activate d by the sleep instruc- tion. see table 7-2 for a summary. if an enabled interrupt occurs while the mcu is in a sleep mode, the mcu wakes up. the mcu is then halted for four cycles in addition to the st art-up time, executes the interrupt routine, and resumes execution from the instruction followi ng sleep. the contents of the register file and sram are unaltered when the device wakes up from sleep. if a reset occurs during sleep mode, the mcu wakes up and executes from the reset vector. note that if a level triggered interrupt is used for wake-up the changed level must be held for some time to wake up the mcu (and for the mcu to enter the interrupt service routine). see ?external interrupts? on page 51 for details. 7.1.1 idle mode when the sm[1:0] bits are written to 00, the sleep instruction makes the mcu enter idle mode, stopping the cpu but allowing analog compar ator, adc, usi, timer/counter, watchdog, and the interrupt system to continue operati ng. this sleep mode basically halts clk cpu and clk flash , while allowing the ot her clocks to run. idle mode enables the mcu to wake up from external triggered interrupts as well as internal ones like the timer overflow. if wake-up from the analog comparator interrupt is not required, table 7-1. active clock domains and wake-up sources in the different sleep modes active clock domains osc illators wake-up sources sleep mode clk cpu clk flash clk io clk adc clk pck main clock source enabled int0 and pin change spm/eeprom ready usi start condition adc other i/o watchdog interrupt idle xxx x xxxxxx adc noise reduction xxx (1) xxx x power-down x (1) xx 36 2586n?avr?04/11 attiny25/45/85 the analog comparator can be powered down by setting the acd bit in ?acsr ? analog com- parator control and status register? on page 124 . this will reduce power consumption in idle mode. if the adc is enabled, a conversion starts automatically when this mode is entered. 7.1.2 adc noise reduction mode when the sm[1:0] bits are written to 01, the sleep instruction makes the mcu enter adc noise reduction mode, stopping the cpu but allowing the adc, the external interrupts, and the watchdog to continue operating (if enabled). this sleep mode halts clk i/o , clk cpu , and clk flash , while allowing the ot her clocks to run. this improves the noise environment for the ad c, enabling higher resolution measurements. if the adc is enabled, a conversion starts automatically when this mode is entered. apart form the adc conversion complete interrupt, only an external reset, a watchdog reset, a brown-out reset, an spm/eeprom ready inte rrupt, an external level interr upt on int0 or a pin change interrupt can wake up the mcu from adc noise reduction mode. 7.1.3 power-down mode when the sm[1:0] bits are written to 10, the sleep instruction makes the mcu enter power- down mode. in this mode, the oscillator is stopp ed, while the external in terrupts, the usi start condition detection and the watchdog continue operating (if enabled). only an external reset, a watchdog reset, a brown-out reset, usi start condition interupt, an external level interrupt on int0 or a pin change interrupt can wake up the mcu. this sleep mode halts all generated clocks, allowing operation of asynchronous modules only. 7.2 software bod disable when the brown-out detector (bod) is enabled by bodlevel fuses (see table 20-4 on page 152 ), the bod is actively monitoring the supply vo ltage during a sleep period. in some devices it is possible to save power by disabling the bod by software in power-down sleep mode. the sleep mode power consumption will t hen be at the same level as when bod is globally disabled by fuses. if bod is disabled by software, the bod function is turned off immediately after entering the sleep mode. upon wake-up from sleep, bod is automatically enabled again. this ensures safe operation in case the v cc level has dropped during the sleep period. when the bod has been disabled, the wake-up ti me from sleep mode will be the same as that for wakeing up from reset. the user must manually configure the wake up times such that the bandgap reference has time to start and the bod is working correctly before the mcu continues executing code. see su t[1:0] and cksel[3:0] fuse bits in table ?fuse low byte? on page 153 bod disable is controlled by the bods (bod sleep) bit of mcu control register, see ?mcucr ? mcu control register? on page 38 . writing this bit to one turn s off bod in po wer-down, while writing a zero keeps the bod active. the de fault setting is zero, i.e. bod active. writing to the bods bit is controlled by a timed sequence and an enable bit, see ?mcucr ? mcu control register? on page 38 . 37 2586n?avr?04/11 attiny25/45/85 7.2.1 limitations bod disable functionality has been implemented in the following devices, only: ? attiny25, revision e, and newer ? attiny45, revision d, and newer ? attiny85, revision c, and newer revisions are marked on the device pack age and can be located as follows: ? bottom side of packages 8p3 and 8s2 ? top side of package 20m1 7.3 power reduction register the power reduction register (prr), see ?prr ? power reduction register? on page 39 , pro- vides a method to reduce power consumption by stopping the clock to individual peripherals. the current state of the peripheral is frozen and the i/o registers can not be read or written. resources used by the peripheral when stopping the clock will remain occupied, hence the peripheral should in most cases be disabled be fore stopping the clock. waking up a module, which is done by clearing the bit in prr, puts the module in the same state as before shutdown. module shutdown can be used in idle mode and ac tive mode to significantly reduce the overall power consumption. in all other sleep modes, the clock is already stopped. see ?supply current of i/o modules? on page 182 for examples. 7.4 minimizing power consumption there are several issues to consider when trying to minimize the power consumption in an avr controlled system. in general, sleep modes should be used as much as possible, and the sleep mode should be selected so that as few as possi ble of the device?s functions are operating. all functions not needed should be disabled. in particular, the following modules may need special consideration when trying to achieve th e lowest possible power consumption. 7.4.1 analog to digital converter if enabled, the adc will be enabled in all sleep modes. to save power, the adc should be dis- abled before entering any sleep mode. when the adc is turned off and on again, the next conversion will be an extended conversion. refer to ?analog to digital converter? on page 126 for details on adc operation. 7.4.2 analog comparator when entering idle mode, the analog comparator should be disabled if not used. when entering adc noise reduction mode, the analog comparat or should be disabled. in the other sleep modes, the analog comparator is automatically di sabled. however, if the analog comparator is set up to use the internal voltage reference as input, the analog comparator should be dis- abled in all sleep modes. ot herwise, the internal volt age reference will be enabled, independent of sleep mode. refer to ?analog comparator? on page 123 for details on how to configure the analog comparator. 38 2586n?avr?04/11 attiny25/45/85 7.4.3 brown-out detector if the brown-out detector is not needed in the application, this module should be turned off. if the brown-out detector is enabled by the bodlevel fuses, it will be enabled in all sleep modes, and hence, always consume power. in the deeper sleep modes, this will contribute significantly to the total current consumption. see ?brown-out detection? on page 43 and ?software bod dis- able? on page 36 for details on how to configure the brown-out detector. 7.4.4 internal voltage reference the internal voltage referenc e will be enabled when needed by the brown-out de tection, the analog comparator or the adc. if these modules are disabled as described in the sections above, the internal voltage refe rence will be disabled and it w ill not be consuming power. when turned on again, the user must allow the reference to start up before the output is used. if the reference is kept on in sleep mode, the output can be used immediately. refer to ?internal volt- age reference? on page 44 for details on the start-up time. 7.4.5 watchdog timer if the watchdog timer is not needed in the application, this module should be turned off. if the watchdog timer is enabled, it will be enabled in all sleep modes, and hence, always consume power. in the deeper slee p modes, this will contribute signific antly to the total current consump- tion. refer to ?watchdog timer? on page 44 for details on how to configure the watchdog timer. 7.4.6 port pins when entering a sleep mode, all port pins should be configured to use minimum power. the most important thing is then to ensure that no pins drive resistive loads. in sleep modes where both the i/o clock (clk i/o ) and the adc clock (clk adc ) are stopped, the input buffers of the device will be disabled. this ensu res that no power is consumed by the input logic when not needed. in some cases, the input logic is needed for detec ting wake-up conditions, and it will then be enabled. refer to the section ?digital input enable and sleep modes? on page 59 for details on which pins are enabled. if the input buffer is enabled and the input signal is left floating or has an analog signal level close to v cc /2, the input buffer will use excessive power. for analog input pins, the digital input buffer should be disabled at all times. an analog signal level close to v cc /2 on an input pin can cause significant current even in active mode. digital input buffers can be disabled by writing to the digital input disable register (didr0). refer to ?didr0 ? digital input disable register 0? on page 125 for details. 7.5 register description 7.5.1 mcucr ? mcu control register the mcu control register contains control bits for power management. ? bit 7 ? bods: bod sleep bod disable functionality is available in some devices, only. see ?limitations? on page 37 . bit 76543210 0x35 bods pud se sm1 sm0 bodse isc01 isc00 mcucr read/write r r/w r/w r/w r/w r r/w r/w initial value00000000 39 2586n?avr?04/11 attiny25/45/85 in order to disable bod during sleep (see table 7-1 on page 35 ) the bods bit must be written to logic one. this is controlled by a timed sequence and the enable bit, bo dse in mcucr. first, both bods and bodse must be set to one. second, within four clock cycles, bods must be set to one and bodse must be set to zero. the bods bit is active three clock cycles after it is set. a sleep instruction must be executed while bods is active in order to turn off the bod for the actual sleep mode. the bods bit is auto matically cleared after three clock cycles. in devices where sleeping bod has not been implem ented this bit is unused and will always read zero. ? bit 5 ? se: sleep enable the se bit must be written to logic one to make the mcu enter the sleep mode when the sleep instruction is executed. to avoid the mcu enteri ng the sleep mode unless it is the programmer?s purpose, it is recommended to write the sleep enable (se) bit to one just before the execution of the sleep instruction and to clear it immediately af ter waking up. ? bits 4:3 ? sm[1:0]: sleep mode select bits 1 and 0 these bits select between the three available sleep modes as shown in table 7-2 . ? bit 2 ? bodse: bod sleep enable bod disable functionality is available in some devices, only. see ?limitations? on page 37 . the bodse bit enables setting of bods control bit, as explained on bods bit description. bod disable is controlled by a timed sequence. this bit is unused in devices where software bod disable has not been implemented and will read as zero in those devices. 7.5.2 prr ? power reduction register the power reduction register provides a met hod to reduce power consumption by allowing peripheral clock signals to be disabled. ? bits 7:4 ? res: reserved bits these bits are reserved bits in the attiny25/45/85 and will always read as zero. ? bit 3 ? prtim1: power reduction timer/counter1 writing a logic one to this bit shuts down the timer/counter1 module. when the timer/counter1 is enabled, operation will cont inue like before the shutdown. table 7-2. sleep mode select sm1 sm0 sleep mode 00idle 0 1 adc noise reduction 1 0 power-down 11reserved bit 76543 2 10 0x20 ? ? ? ? prtim1 prtim0 prusi pradc prr read/write r r r r r/w r/w r/w r/w initial value 0 0 0 0 0 0 0 0 40 2586n?avr?04/11 attiny25/45/85 ? bit 2 ? prtim0: power reduction timer/counter0 writing a logic one to this bit shuts down the timer/counter0 module. when the timer/counter0 is enabled, operation will cont inue like before the shutdown. ? bit 1 ? prusi: power reduction usi writing a logic one to this bit shuts down t he usi by stopping the clock to the module. when waking up the usi again, the usi should be re initialized to ensure proper operation. ? bit 0 ? pradc: power reduction adc writing a logic one to this bit shuts down the adc. the adc must be disabled before shut down. note that the adc clock is also used by some parts of the analog comparator, which means that the analogue comparator can not be used when this bit is high. 41 2586n?avr?04/11 attiny25/45/85 8. system control and reset 8.1 resetting the avr during reset, all i/o registers are set to their initial values, and the program starts execution from the reset vector. the instruction placed at the reset vector must be a rjmp ? relative jump ? instruction to the reset handling routine. if the program never enables an interrupt source, the interrupt vectors are not used, and regular program code can be placed at these locations. the circuit diagram in figure 8-1 shows the reset logic. electrical parameters of the reset circuitry are given in ?system and reset characteristics? on page 170 . figure 8-1. reset logic the i/o ports of the avr are immediately reset to their initial state when a reset source goes active. this does not require any clock source to be running. after all reset sources have gone inactive, a delay counter is invoked, stretching the internal reset. this allows the power to reach a stable level before normal operation starts. the time-out period of the delay counter is defined by the user through the sut and cksel fuses. the dif- ferent selections for the delay period are presented in ?clock sources? on page 25 . 8.2 reset sources the attiny25/45/85 has four sources of reset: ? power-on reset. the mcu is reset when the supply voltage is below the power-on reset threshold (v pot ). ? external reset. the mcu is reset when a low level is present on the reset pin for longer than the minimum pulse length. ? watchdog reset. the mcu is reset when the watchdog timer period expires and the watchdog is enabled. ? brown-out reset. the mcu is re set when the supply voltage v cc is below the brown-out reset threshold (v bot ) and the brown-out detector is enabled. mcu status register (mcusr) brown-out reset circuit bodlevel[2:0] delay counters reset circuit reset vcc watchdog timer internal reset counter reset cksel[3:0] ck timeout wdrf borf extrf porf data bus r s q clock generator spike filter pull-up resistor watchdog oscillator sut[1:0] power-on reset circuit 42 2586n?avr?04/11 attiny25/45/85 8.2.1 power-on reset a power-on reset (por) pulse is generated by an on-chip detection circuit. the detection level is defined in ?system and reset characteristics? on page 170 . the por is activated whenever v cc is below the detection level. the por circuit can be used to trigger the start-up reset, as well as to detect a fa ilure in supply voltage. a power-on reset (por) circuit ensures that the device is reset from power-on. reaching the power-on reset threshold voltage invokes the delay counter, which determines how long the device is kept in reset after v cc rise. the reset signal is acti vated again, without any delay, when v cc decreases below the detection level. figure 8-2. mcu start-up, reset tied to v cc figure 8-3. mcu start-up, reset extended externally 8.2.2 external reset an external reset is generated by a low level on the reset pin if enabled. reset pulses longer than the minimum pulse width (see ?system and reset characteristics? on page 170 ) will gener- ate a reset, even if the clock is not running. shorter pulses are not guaranteed to generate a reset. when the applied signal reaches the reset threshold voltage ? v rst ? on its positive edge, the delay counter starts the mcu after the time-out period ? t tout ? has expired. v reset time-out internal reset t tout v pot v rst cc reset time-out internal reset t tout v pot v rst v cc 43 2586n?avr?04/11 attiny25/45/85 figure 8-4. external reset during operation 8.2.3 brown-out detection attiny25/45/85 has an on-chip brown-out detection (bod) circuit for monitoring the v cc level during operation by comparing it to a fixed trigger level. the trigger level for the bod can be selected by the bodlevel fuses. the trigger level has a hysteresis to ensure spike free brown-out detection. the hysteresis on the detection level should be interpreted as v bot+ = v bot + v hyst /2 and v bot- = v bot - v hyst /2. when the bod is enabled, and v cc decreases to a value below the trigger level (v bot- in figure 8-5 ), the brown-out reset is immediately activated. when v cc increases above the trigger level (v bot+ in figure 8-5 ), the delay counter starts the mcu after the time-out period t tout has expired. the bod circuit will only detect a drop in v cc if the voltage stays below the trigger level for lon- ger than t bod given in ?system and reset characteristics? on page 170 . figure 8-5. brown-out reset during operation 8.2.4 watchdog reset when the watchdog times out, it will generate a short reset pulse of one ck cycle duration. on the falling edge of this pulse, the delay timer starts counting the time-out period t tout . refer to ?watchdog timer? on page 44 for details on operation of the watchdog timer. cc v cc reset time-out internal reset v bot- v bot+ t tout 44 2586n?avr?04/11 attiny25/45/85 figure 8-6. watchdog reset during operation 8.3 internal voltage reference attiny25/45/85 features an internal bandgap reference. this reference is used for brown-out detection, and it can be used as an input to the analog comparator or the adc. 8.3.1 voltage reference enable signals and start-up time the voltage reference has a start-up time that may influence the way it should be used. the start-up time is given in ?system and reset characteristics? on page 170 . to save power, the reference is not always turned on. the reference is on during the following situations: 1. when the bod is enabled (by prog ramming the bodlevel [2:0] fuse bits). 2. when the bandgap reference is connected to the analog comparator (by setting the acbg bit in acsr). 3. when the adc is enabled. thus, when the bod is not enabled, after setting the acbg bit or enabling the adc, the user must always allow the reference to start up before the output from the analog comparator or adc is used. to reduce power consumption in power-down mode, the user can avoid the three conditions above to ensure that the reference is turned off before entering power-down mode. 8.4 watchdog timer the watchdog timer is clocked fr om an on-chip oscillator which runs at 128 khz. by controlling the watchdog timer prescaler, the watchdog reset interval can be adjusted as shown in table 8-3 on page 48 . the wdr ? watchdog reset ? instruction resets the watchdog timer. the watchdog timer is also reset when it is disabled and when a chip reset occurs. ten different clock cycle periods can be selected to determine the reset period. if the reset period expires without another watchdog reset, the attiny25/45/85 resets and executes from the reset vec- tor. for timing details on the watchdog reset, refer to table 8-3 on page 48 . the wathdog timer can also be configured to generate an interrupt instead of a reset. this can be very helpful when using the watchdog to wake-up from power-down. to prevent unintentional disabling of the watchdog or unintentional change of time-out period, two different safety levels are selected by the fuse wdton as shown in table 8-1 refer to ck cc 45 2586n?avr?04/11 attiny25/45/85 ?timed sequences for changing the configuration of the watchdog timer? on page 45 for details. figure 8-7. watchdog timer 8.4.1 timed sequences for changing the configuration of the watchdog timer the sequence for changing configuration differs slightly between the two safety levels. separate procedures are described for each level. 8.4.1.1 safety level 1 in this mode, the watchdog time r is initially disabled, but can be enabled by writing the wde bit to one without any restriction. a timed sequence is needed when disabling an enabled watch- dog timer. to disable an enabled watchdog timer, the following procedure must be followed: 1. in the same operation, write a logic one to wdce and wde. a logic one must be writ- ten to wde regardless of the previous value of the wde bit. 2. within the next four clock cycles, in the same operation, write the wde and wdp bits as desired, but with the wdce bit cleared. 8.4.1.2 safety level 2 in this mode, the watchdog time r is always enabled, and the wde bit will always read as one. a timed sequence is needed when changing the watchdog time-out period. to change the watchdog time-out, the following procedure must be followed: 1. in the same operation, write a logical one to wdce and wde. even though the wde always is set, the wde must be written to one to start the timed sequence. 2. within the next four clock cycles, in the same operation, write the wdp bits as desired, but with the wdce bit cleared. the value written to the wde bit is irrelevant. table 8-1. wdt configuration as a function of the fuse settings of wdton wdton safety level wdt initial state how to disable the wdt how to change time- out unprogrammed 1 disabled timed sequence no limitations programmed 2 enabled always enabled timed sequence osc/2k osc/4k osc/8k osc/16k osc/32k osc/64k osc/128k osc/256k osc/512k osc/1024k mcu reset watchdog prescaler 128 khz oscillator watchdog reset wdp0 wdp1 wdp2 wdp3 wde 46 2586n?avr?04/11 attiny25/45/85 8.4.2 code example the following code example shows one assembly and one c function for turning off the wdt. the example assumes that interrupts are controlled (e.g., by disabling interrupts globally) so that no interrupts will occur during execution of these functions. note: 1. see ?code examples? on page 6 . 8.5 register description 8.5.1 mcusr ? mcu status register the mcu status register provides information on which reset source caused an mcu reset. ? bits 7:4 ? res: reserved bits these bits are reserved bits in the attiny25/45/85 and will always read as zero. assembly code example (1) wdt_off: wdr ; clear wdrf in mcusr ldi r16, (0< 48 2586n?avr?04/11 attiny25/45/85 ? bit 4 ? wdce: watchdog change enable this bit must be set when the wde bit is writte n to logic zero. otherwis e, the watchdog will not be disabled. once written to one, hardware will clear this bit after four clock cycles. refer to the description of the wde bit for a watchdog disable procedure. this bit must also be set when changing the prescaler bits. see ?timed sequences for changing the configuration of the watchdog timer? on page 45 . ? bit 3 ? wde: watchdog enable when the wde is written to logic one, the watchdog timer is enabled, and if the wde is written to logic zero, the watchdog timer function is di sabled. wde can only be cleared if the wdce bit has logic level one. to disable an enabled watchdog timer, the following procedure must be followed: 1. in the same operation, write a logic one to wdce and wde. a logic one must be writ- ten to wde even though it is set to one before the disable operation starts. 2. within the next four clock cycles, write a logic 0 to wde. this disables the watchdog. in safety level 2, it is not possible to disable the watchdog timer, even with the algorithm described above. see ?timed sequences for changing the configuration of the watchdog timer? on page 45 . in safety level 1, wde is overridden by wdrf in mcusr. see ?mcusr ? mcu status regis- ter? on page 46 for description of wdrf. this means that wde is always set when wdrf is set. to clear wde, wdrf must be cleared before disabling the watchdog with the procedure described above. this feature ensures multiple re sets during conditions causing failure, and a safe start-up after the failure. note: if the watchdog timer is not going to be used in the application, it is important to go through a watchdog disable procedure in the initialization of the device. if the watchdog is accidentally enabled, for example by a runaway pointer or brown-out condition, the device will be reset, which in turn will lead to a new watchdog reset. to avoi d this situation, the app lication software should always clear the wdrf flag and the wde control bit in the initialization routine. ? bits 5, 2:0 ? wdp[3:0]: watchdog timer prescaler 3, 2, 1, and 0 the wdp[3:0] bits determine the watchdog timer prescaling when the watchdog timer is enabled. the different prescaling values and their corresponding timeout periods are shown in table 8-3 . table 8-3. watchdog timer prescale select wdp3 wdp2 wdp1 wdp0 number of wdt oscillator cycles typical time-out at v cc = 5.0v 0 0 0 0 2k (2048) cycles 16 ms 0 0 0 1 4k (4096) cycles 32 ms 0 0 1 0 8k (8192) cycles 64 ms 0 0 1 1 16k (16384) cycles 0.125 s 0 1 0 0 32k (32764) cycles 0.25 s 0 1 0 1 64k (65536) cycles 0.5 s 0 1 1 0 128k (131072) cycles 1.0 s 0 1 1 1 256k (262144) cycles 2.0 s 1 0 0 0 512k (524288) cycles 4.0 s 49 2586n?avr?04/11 attiny25/45/85 note: 1. if selected, one of the valid settings below 0b1010 will be used. 1 0 0 1 1024k (1048576) cycles 8.0 s 1010 reserved (1) 1011 1100 1101 1110 1111 table 8-3. watchdog timer prescale select (continued) wdp3 wdp2 wdp1 wdp0 number of wdt oscillator cycles typical time-out at v cc = 5.0v 50 2586n?avr?04/11 attiny25/45/85 9. interrupts this section describes the specifics of the interrupt handling as performed in attiny25/45/85. for a general explanation of the avr interrupt handling, refer to ?reset and interrupt handling? on page 12 . 9.1 interrupt vectors in attiny25/45/85 the interrupt vectors of attiny25/45/85 are described in table 9-1 below. if the program never enables an interrupt source, the interrupt vectors are not used, and regular program code can be placed at these locations. table 9-1. reset and interrupt vectors vector no. program address source interrupt definition 1 0x0000 reset external pin, power-on reset, brown-out reset, watchdog reset 2 0x0001 int0 external interrupt request 0 3 0x0002 pcint0 pin change interrupt request 0 4 0x0003 timer1_compa timer/counter1 compare match a 5 0x0004 timer1_ovf timer/counter1 overflow 6 0x0005 timer0_ovf timer/counter0 overflow 7 0x0006 ee_rdy eeprom ready 8 0x0007 ana_comp analog comparator 9 0x0008 adc adc conversion complete 10 0x0009 timer1_compb timer/counter1 compare match b 11 0x000a timer0_compa timer/ counter0 compare match a 12 0x000b timer0_compb timer/ counter0 compare match b 13 0x000c wdt watchdog time-out 14 0x000d usi_start usi start 15 0x000e usi_ovf usi overflow 51 2586n?avr?04/11 attiny25/45/85 a typical and general setup for interrupt vector addresses in attiny25/45/85 is shown in the pro- gram example below. note: see ?code examples? on page 6 . 9.2 external interrupts the external interrupts are triggered by the int0 pin or any of the pcint[5:0] pins. observe that, if enabled, the interrupts will trigger even if the int0 or pcint[5:0] pins are configured as outputs. this feature provides a way of generating a software interrupt. pin change interrupts pci will trigger if any enabled pcint[5:0] pin toggles. the pcmsk register control which pins contribute to the pin change interrupts. pin change interrupts on pcint[5:0] are detected asyn- chronously. this implies that these interrupts can be used for waking the part also from sleep modes other than idle mode. the int0 interrupts can be triggered by a falling or rising edge or a low level. this is set up as indicated in the specification for the mcu control register ? mcucr. when the int0 interrupt is enabled and is configured as leve l triggered, the interr upt will trigger as long as the pin is held low. note that recognition of falling or rising edge interrupts on int0 requires the presence of an i/o clock, described in ?clock systems and their distribution? on page 23 . 9.2.1 low level interrupt a low level interrupt on int0 is detected asynch ronously. this implies that this interrupt can be used for waking the part also from sleep modes other than idle mode. the i/o clock is halted in all sleep modes except idle mode. assembly code example .org 0x0000 ;set address of next statement rjmp reset ; address 0x0000 rjmp int0_isr ; address 0x0001 rjmp pcint0_isr ; address 0x0002 rjmp tim1_compa_isr ; address 0x0003 rjmp tim1_ovf_isr ; address 0x0004 rjmp tim0_ovf_isr ; address 0x0005 rjmp ee_rdy_isr ; address 0x0006 rjmp ana_comp_isr ; address 0x0007 rjmp adc_isr ; address 0x0008 rjmp tim1_compb_isr ; address 0x0009 rjmp tim0_compa_isr ; address 0x000a rjmp tim0_compb_isr ; address 0x000b rjmp wdt_isr ; address 0x000c rjmp usi_start_isr ; address 0x000d rjmp usi_ovf_isr ; address 0x000e reset: ; main program start 52 2586n?avr?04/11 attiny25/45/85 note that if a level triggered interrupt is used for wake-up from power-down, the required level must be held long enough for the mcu to complete the wake-up to trigger the level interrupt. if the level disappears before the end of the start-up ti me, the mcu will still wake up, but no inter- rupt will be generated. the start- up time is defined by the su t and cksel fuses as described in ?system clock and clock options? on page 23 . if the low level on the interrupt pin is removed before the device has woken up then program execution will not be diverted to the interrupt service ro utine but continue from the instruction fol- lowing the sleep command. 9.2.2 pin change interrupt timing an example of timing of a pin change interrupt is shown in figure 9-1 . figure 9-1. timing of pin change interrupts clk pcint(0) pin_lat pin_sync pcint_in_(0) pcint_syn pcint_setflag pcif pcint(0) pin_sync pcint_syn pin_lat d q le pcint_setflag pcif clk clk pcint(0) in pcmsk(x) pcint_in_(0) 0 x 53 2586n?avr?04/11 attiny25/45/85 9.3 register description 9.3.1 mcucr ? mcu control register the external interrupt control register a contains control bits for interrupt sense control. ? bits 1:0 ? isc0[1:0]: interrupt sense control 0 bit 1 and bit 0 the external interrupt 0 is activated by the exte rnal pin int0 if the sreg i-flag and the corre- sponding interrupt mask are set. the level and edges on the external int0 pin that activate the interrupt are defined in table 9-2 . the value on the int0 pin is sampled before detecting edges. if edge or toggle interrupt is selected, pulses that last longer than one clock period will generate an interrupt. shorter pulses are not guaranteed to generate an interrupt. if low level interrupt is selected, the low level must be held until the completion of the currently executing instruction to generate an interrupt. 9.3.2 gimsk ? general interrupt mask register ? bits 7, 4:0 ? res: reserved bits these bits are reserved bits in the attiny25/45/85 and will always read as zero. ? bit 6 ? int0: external interrupt request 0 enable when the int0 bit is set (one) and the i-bit in the status register (sreg) is set (one), the exter- nal pin interrupt is enabled. the interrupt sense control0 bits 1/0 (isc01 and isc00) in the mcu control register (mcucr) define whether the external interrupt is activated on rising and/or fall- ing edge of the int0 pin or level sensed. activi ty on the pin will cause an interrupt request even if int0 is configured as an output. the corresponding interrupt of external interrupt request 0 is executed from the int0 interrupt vector. ? bit 5 ? pcie: pin change interrupt enable when the pcie bit is set (one) and the i-bit in the status register (sreg) is set (one), pin change interrup t is enabled. any change on any enabled pcint[5:0] pin will cause an interrupt. the corresponding interrupt of pin change interrupt request is executed from the pci interrupt vector. pcint[5:0] pins are enabled individually by the pcmsk0 register. bit 76543210 0x35 bods pud se sm1 sm0 bodse isc01 isc00 mcucr read/write r r/w r/w r/w r/w r r/w r/w initial value00000000 table 9-2. interrupt 0 sense control isc01 isc00 description 0 0 the low level of int0 generates an interrupt request. 0 1 any logical change on int0 generates an interrupt request. 1 0 the falling edge of int0 generates an interrupt request. 1 1 the rising edge of int0 generates an interrupt request. bit 76543210 0x3b ?int0pcie?????gimsk read/write rr/wr/wrrrrr initial value00000000 54 2586n?avr?04/11 attiny25/45/85 9.3.3 gifr ? general interrupt flag register ? bits 7, 4:0 ? res: reserved bits these bits are reserved bits in the attiny25/45/85 and will always read as zero. ? bit 6 ? intf0: external interrupt flag 0 when an edge or logic change on the int0 pin triggers an interrupt request, intf0 becomes set (one). if the i-bit in sreg and the int0 bit in gimsk are set (o ne), the mcu will jump to the cor- responding interrupt vector. the flag is cleared when the interrupt routine is executed. alternatively, the flag can be cleared by writing a logical one to it. this flag is always cleared when int0 is configured as a level interrupt. ? bit 5 ? pcif: pin change interrupt flag when a logic change on any pcint[5:0] pin triggers an interrupt request, pcif becomes set (one). if the i-bit in sreg and the pcie bit in gimsk are set (one), the mcu will jump to the cor- responding interrupt vector. the flag is cleared when the interrupt routine is executed. alternatively, the flag can be cleared by writing a logical one to it. 9.3.4 pcmsk ? pin change mask register ? bits 7:6 ? res: reserved bits these bits are reserved bits in the attiny25/45/85 and will always read as zero. ? bits 5:0 ? pcint[5:0]: pin change enable mask 5:0 each pcint[5:0] bit selects whether pin c hange interrupt is enabled on the corresponding i/o pin. if pcint[5:0] is set and the pcie bit in gimsk is set, pin change interrupt is enabled on the corresponding i/o pin. if pcint[5:0] is cleared, pin change interrupt on the corresponding i/o pin is disabled. bit 76543210 0x3a ?intf0pcif?????gifr read/write rr/wr/wrrrrr initial value00000000 bit 76543210 0x15 ? ? pcint5 pcint4 pcint3 pcint2 pcint1 pcint0 pcmsk read/write r r r/w r/w r/w r/w r/w r/w initial value00000000 55 2586n?avr?04/11 attiny25/45/85 10. i/o ports 10.1 introduction all avr ports have true read-modi fy-write functionality when used as general digital i/o ports. this means that the direction of one port pin can be changed without unintentionally changing the direction of any other pin with the sbi and cbi instructions. the same applies when chang- ing drive value (if configured as output) or enabling/disabling of pull-up resistors (if configured as input). each output buffer has symmetrical drive characteristics with both high sink and source capability. the pin driver is stro ng enough to drive led displays directly. all port pins have indi- vidually selectable pull-up resistors with a suppl y-voltage invariant resistance. all i/o pins have protection diodes to both v cc and ground as indicated in figure 10-1 . refer to ?electrical char- acteristics? on page 166 for a complete list of parameters. figure 10-1. i/o pin equivalent schematic all registers and bit references in this section are written in general form. a lower case ?x? repre- sents the numbering letter for the port, and a lower case ?n? represents the bit number. however, when using the register or bit defines in a progr am, the precise form must be used. for example, portb3 for bit no. 3 in port b, here documented generally as portxn. the physical i/o regis- ters and bit locations are listed in ?register description? on page 66 . three i/o memory address locations are allocated for each port, one each for the data register ? portx, data direction register ? ddrx, and the port input pins ? pinx. the port input pins i/o location is read only, while the data register and the data direction register are read/write. however, writing a logic one to a bit in the pinx register, will result in a toggle in the correspond- ing bit in the data register. in addition, the pu ll-up disable ? pud bit in mcucr disables the pull-up function for all pins in all ports when set. using the i/o port as general digital i/o is described in ?ports as general digital i/o? on page 56 . most port pins are multiplexed with alternate functions for the peripheral features on the device. how each alternate function interferes with the port pin is described in ?alternate port functions? on page 59 . refer to the individual module sectio ns for a full description of the alter- nate functions. note that enabling the alternate function of some of the port pins does not affect the use of the other pins in the port as general digital i/o. logic r p u s ee fig u re "gener a l digit a l i/o" for det a il s pxn 56 2586n?avr?04/11 attiny25/45/85 10.2 ports as gener al digital i/o the ports are bi-directional i/o ports with optional internal pull-ups. figure 10-2 shows a func- tional description of one i/o-port pin, here generically called pxn. figure 10-2. general digital i/o (1) note: 1. wrx, wpx, wdx, rrx, rpx, and rdx are co mmon to all pins within the same port. clk i/o , sleep, and pud are common to all ports. 10.2.1 configuring the pin each port pin consists of three register bits: ddxn, portxn, and pinxn. as shown in ?register description? on page 66 , the ddxn bits are accessed at the ddrx i/o address, the portxn bits at the portx i/o address, and the pinxn bits at the pinx i/o address. the ddxn bit in the ddrx register selects the direct ion of this pin. if ddxn is written logic one, pxn is configured as an output pin. if ddxn is written logic zero, pxn is configured as an input pin. if portxn is written logic one when the pin is c onfigured as an input pin, the pull-up resistor is activated. to switch the pull-up resistor off, portxn has to be written logic zero or the pin has to be configured as an output pin. the port pins are tri-stated when reset condition becomes active, even if no clocks are running. if portxn is written logic one when the pin is conf igured as an output pin, the port pin is driven high (one). if portxn is written logic zero when the pin is configured as an output pin, the port pin is driven low (zero). clk rpx rrx rdx wdx pud synchronizer wdx: write ddrx wrx: write portx rrx: read portx register rpx: read portx pin pud: pullup disable clk i/o : i/o clock rdx: read ddrx d l q q reset reset q q d q q d clr portxn q q d clr ddxn pinxn data b u s sleep sleep: sleep control pxn i/o wpx 0 1 wrx wpx: write pinx register 57 2586n?avr?04/11 attiny25/45/85 10.2.2 toggling the pin writing a logic one to pinxn toggles the value of portxn, independent on the value of ddrxn. note that the sbi instruction can be used to toggle one single bit in a port. 10.2.3 switching between input and output when switching between tri-state ({ddxn, portxn} = 0b00) and output high ({ddxn, portxn} = 0b11), an intermediate state with either pull-up enabled {ddxn, portxn} = 0b01) or output low ({ddxn, portxn} = 0b10) must occur. norma lly, the pull-up enabled state is fully accept- able, as a high-impedant enviro nment will not notice the differenc e between a strong high driver and a pull-up. if this is not the case, the pud bit in the mcucr register can be set to disable all pull-ups in all ports. switching between input with pull-up and output low generates the same problem. the user must use either the tri-state ({ddxn, portxn} = 0b00) or the output high state ({ddxn, portxn} = 0b10) as an intermediate step. table 10-1 summarizes the control signals for the pin value. 10.2.4 reading the pin value independent of the setting of data direction bit ddxn, the port pin can be read through the pinxn register bit. as shown in figure 10-2 , the pinxn register bit and the preceding latch con- stitute a synchronizer. this is needed to avoid metastability if the physical pin changes value near the edge of the internal clock, but it also introduces a delay. figure 10-3 shows a timing dia- gram of the synchronization when reading an externally applied pin value. the maximum and minimum propagation delays are denoted t pd,max and t pd,min respectively. figure 10-3. synchronization when reading an externally applied pin value table 10-1. port pin configurations ddxn portxn pud (in mcucr) i/o pull-up comment 0 0 x input no tri-state (hi-z) 0 1 0 input yes pxn will source current if ext. pulled low. 0 1 1 input no tri-state (hi-z) 1 0 x output no output low (sink) 1 1 x output no output high (source) xxx in r17, pinx 0x00 0xff instructions sync latch pinxn r17 xxx system clk t pd, max t pd, min 58 2586n?avr?04/11 attiny25/45/85 consider the clock period starting shortly after the first falling edge of the system cl ock. the latch is closed when the clock is low, and goes transpa rent when the clock is high, as indicated by the shaded region of the ?sync latch? signal. the signal value is latched when the system clock goes low. it is clocked into the pinxn register at the succeeding positive clock edge. as indi- cated by the two arrows tpd,max and tpd,min, a single signal tr ansition on the pin will be delayed between ? and 1? system clock period depending upon the time of assertion. when reading back a software assigned pin value, a nop instruction must be inserted as indi- cated in figure 10-4 . the out instruction sets the ?sync latch? signal at the positive edge of the clock. in this case, the delay tpd through the synchronizer is one system clock period. figure 10-4. synchronization when reading a software assigned pin value the following code example shows how to set port b pins 0 and 1 high, 2 and 3 low, and define the port pins from 4 to 5 as input with a pull-up assigned to port pin 4. the resulting pin values are read back again, but as previously discussed, a nop instruction is included to be able to read back the value recently assigned to some of the pins. note: 1. for the assembly program, two temporary registers are used to minimize the time from pull- ups are set on pins 0, 1 and 4, until the direction bits are correctly set, defining bit 2 and 3 as low and redefining bits 0 and 1 as strong high drivers. assembly code example (1) ... ; define pull-ups and set outputs high ; define directions for port pins ldi r16,(1< 61 2586n?avr?04/11 attiny25/45/85 table 10-2 summarizes the function of the overriding signals. the pin and port indexes from fig- ure 10-5 are not shown in the succeeding tables. the overriding signals are generated internally in the modules having the alternate function. the following subsections shortly describe the alternate functions for each port, and relate the overriding signals to the alternate function. refer to the alternate function description for further details. table 10-2. generic description of overriding signals for alternate functions signal name full name description puoe pull-up override enable if this signal is set, the pull-up enable is controlled by the puov signal. if this signal is cleared, the pull-up is enabled when {ddxn, portxn, pud} = 0b010. puov pull-up override value if puoe is set, the pull-up is enabled/disabled when puov is set/cleared, regardless of the setting of the ddxn, portxn, and pud register bits. ddoe data direction override enable if this signal is set, the output driver enable is controlled by the ddov signal. if this signal is cleared, the output driver is enabled by the ddxn register bit. ddov data direction override value if ddoe is set, the output driver is enabled/disabled when ddov is set/cleared, regardless of the setting of the ddxn register bit. pvoe port value override enable if this signal is set and the output driver is enabled, the port value is controlled by the pvov signal. if pvoe is cleared, and the output driver is enabled, the port value is controlled by the portxn register bit. pvov port value override value if pvoe is set, the port value is set to pvov, regardless of the setting of the portxn register bit. ptoe port toggle override enable if ptoe is set, the portxn register bit is inverted. dieoe digital input enable override enable if this bit is set, the digital input enable is controlled by the dieov signal. if this signal is cleared, the digital input enable is determined by mcu state (normal mode, sleep mode). dieov digital input enable override value if dieoe is set, the digital in put is enabled/disabled when dieov is set/cleared, regardl ess of the mcu state (normal mode, sleep mode). di digital input this is the digital input to alternate functions. in the figure, the signal is connected to the output of the schmitt-trigger but before the synchronizer. unless the digital input is used as a clock source, the module with the alternate function will use its own synchronizer. aio analog input/output this is the analog input/output to/from alternate functions. the signal is connected directly to the pad, and can be used bi- directionally. 62 2586n?avr?04/11 attiny25/45/85 10.3.1 alternate functions of port b the port b pins with alternate function are shown in table 10-3 . ? port b, bit 5 ? reset /dw/adc0/pcint5 ? reset : external reset input is active low and enabled by unprogramming (?1?) the rstdisbl fuse. pullup is activated and output driver and digital input are deactivated when the pin is used as the reset pin. ? dw: when the debugwire enable (dwen) fuse is programmed and lock bits are unprogrammed, the debugwire system within th e target device is activated. the reset port pin is configured as a wire-and (open-dr ain) bi-directional i/o pin with pull-up enabled and becomes the communication gateway between target and emulator. ? adc0: analog to digital converter, channel 0 . ? pcint5: pin change interrupt source 5. table 10-3. port b pins alternate functions port pin alternate function pb5 reset :reset pin dw: debugwire i/o adc0: adc input channel 0 pcint5: pin change interrupt, source 5 pb4 xtal2: crystal oscillator output clko: system clock output adc2: adc input channel 2 oc1b: timer/counter1 compare match b output pcint4: pin change interrupt 0, source 4 pb3 xtal1: crystal oscillator input clki: external clock input adc3: adc input channel 3 oc1b : complementary timer/counter1 compare match b output pcint3: pin change interrupt 0, source 3 pb2 sck: serial clock input adc1: adc input channel 1 t0: timer/counter0 clock source usck: usi clock (three wire mode) scl : usi clock (two wire mode) int0: external interrupt 0 input pcint2: pin change interrupt 0, source 2 pb1 miso: spi master data input / slave data output ain1: analog comparator, negative input oc0b: timer/counter0 compare match b output oc1a: timer/counter1 compare match a output do: usi data output (three wire mode) pcint1:pin change interrupt 0, source 1 pb0 mosi:: spi master data ou tput / slave data input ain0: analog comparator, positive input oc0a: timer/counter0 compare match a output oc1a : complementary timer/counter1 compare match a output di: usi data input (three wire mode) sda: usi data input (two wire mode) aref: external analog reference pcint0: pin change interrupt 0, source 0 63 2586n?avr?04/11 attiny25/45/85 ? port b, bit 4 ? xtal2/clko/adc2/oc1b/pcint4 ? xtal2: chip clock oscillator pin 2. used as clock pin for all chip clock sources except internal calibrateble rc oscillator and external clock. when used as a clock pin, the pin can not be used as an i/o pin. when using internal calibratable rc oscillator or external clock as a chip clock sources, pb4 serves as an ordinary i/o pin. ? clko: the devided system clock can be output on the pin pb4. the divided system clock will be output if the ckout fuse is programmed, regardless of the portb4 and ddb4 settings. it will also be output during reset. ? adc2: analog to digital converter, channel 2 . ? oc1b: output compare match output: the pb4 pin can serve as an external output for the timer/counter1 compare match b when configured as an output (ddb4 set). the oc1b pin is also the output pin for the pwm mode timer function. ? pcint4: pin change interrupt source 4. ? port b, bit 3 ? xtal1/clki/adc3/oc1b /pcint3 ? xtal1: chip clock oscillator pin 1. used fo r all chip clock sources except internal calibrateble rc oscillator. when used as a clock pin, the pin can not be used as an i/o pin. ? clki: clock input from an external clock source, see ?external clock? on page 26 . ? adc3: analog to digital converter, channel 3 . ?oc1b : inverted output compare match output: the pb3 pin can serve as an external output for the timer/counter1 compare match b when configured as an output (ddb3 set). the oc1b pin is also the inverted output pin for the pwm mode timer function. ? pcint3: pin change interrupt source 3. ? port b, bit 2 ? sck/adc1 /t0/usck/scl /int0/pcint2 ? sck: master clock output, slave clock input pin for spi channel. when the spi is enabled as a slave, this pin is configured as an input r egardless of the setting of ddb2. when the spi is enabled as a master, the data direction of this pin is controlled by ddpb2. when the pin is forced by the spi to be an input, the pull-up can still be controlled by the portb2 bit. ? adc1: analog to digital converter, channel 1 . ? t0: timer/counter0 counter source. ? usck: three-wire mode univer sal serial interface clock. ? scl: two-wire mode serial clock for usi two-wire mode. ? int0: external interrupt source 0. ? pcint2: pin change interrupt source 2. ? port b, bit 1 ? miso/ain1/oc0b/oc1a/do/pcint1 ? miso: master data input, slave data output pin for spi channel. when the spi is enabled as a master, this pin is configured as an input regardless of the setting of ddb1. when the spi is enabled as a slave, the data direction of this pin is controlled by ddb1. when the pin is forced by the spi to be an input, the pull-up can still be controlled by the portb1 bit. ? ain1: analog comparator negative input. configure the port pin as input with the internal pull-up switched off to avoid the digital port function from interfering with the function of the analog comparator. ? oc0b: output compare match output. the pb1 pin can serve as an external output for the timer/counter0 compare match b. the pb1 pin has to be configured as an output (ddb1 64 2586n?avr?04/11 attiny25/45/85 set (one)) to serve this function. the oc0b pin is also the output pin for the pwm mode timer function. ? oc1a: output compare match output: the pb1 pin can serve as an external output for the timer/counter1 compare match b when configured as an output (ddb1 set). the oc1a pin is also the output pin for the pwm mode timer function. ? do: three-wire mode universal serial interface data output. three-wire mode data output overrides portb1 value and it is driven to the port when data direction bit ddb1 is set (one). portb1 still enables the pull-up, if the dire ction is input and po rtb1 is set (one). ? pcint1: pin change interrupt source 1. ? port b, bit 0 ? mosi/ain0/oc0a/oc1a /di/sda/aref/pcint0 ? mosi: spi master data output, slave data input for spi channel. when the spi is enabled as a slave, this pin is configured as an input r egardless of the setting of ddb0. when the spi is enabled as a master, the data direction of this pin is controlled by ddb0. when the pin is forced by the spi to be an input, the pull-up can still be controlled by the portb0 bit. ? ain0: analog comparator positive input. configure the port pin as input with the internal pull- up switched off to avoid the digital port function from interfering with the function of the analog comparator. ? oc0a: output compare match output. the pb0 pin can serve as an external output for the timer/counter0 compare match a when configured as an output (ddb0 set (one)). the oc0a pin is also the output pin for the pwm mode timer function. ?oc1a : inverted output compare match output: the pb0 pin can serve as an external output for the timer/counter1 compare match b when configured as an output (ddb0 set). the oc1a pin is also the inverted output pin for the pwm mode timer function. ? sda: two-wire mode serial interface data. ? aref: external analog reference for adc. pullup and output driver are disabled on pb0 when the pin is used as an external reference or internal voltage reference with external capacitor at the aref pin. ? di: data input in usi three-wire mode. usi th ree-wire mode does not override normal port functions, so pin must be configure as an input for di function. ? pcint0: pin change interrupt source 0. table 10-4 and table 10-5 relate the alternate functions of port b to the overriding signals shown in figure 10-5 on page 60 . 65 2586n?avr?04/11 attiny25/45/85 note: 1. 1 when the fuse is ?0? (programmed). table 10-4. overriding signals for alternate functions in pb[5:3] signal name pb5/reset / adc0/pcint5 pb4/adc2/xtal2/ oc1b/pcint4 pb3/adc3/xtal1/ oc1b /pcint3 puoe rstdisbl (1) ? dwen (1) 00 puov100 ddoe rstdisbl (1) ? dwen (1) 00 ddov debugwire transmit 0 0 pvoe 0 oc1b enable oc1b enable pvov 0 oc1b oc1b ptoe000 dieoe rstdisbl (1) + (pcint5 ? pcie + adc0d) pcint4 ? pcie + adc2d pcint3 ? pcie + adc3d dieov adc0d adc2d adc3d di pcint5 input pcint4 input pcint3 input aio reset input, adc0 in put adc2 input adc3 input table 10-5. overriding signals for alternate functions in pb[2:0] signal name pb2/sck/adc1/t0/ usck/scl/int0/pcint2 pb1/miso/do/ain1/ oc1a/oc0b/pcint1 pb0/mosi/di/sda/ain0/ar ef/oc1a /oc0a/ pcint0 puoe usi_two_wire 0 usi_two_wire puov000 ddoe usi_two_wire 0 usi_two_wire ddov (usi_scl_hold + portb2 ) ? ddb2 0(sda + portb0 ) ? ddb0 pvoe usi_two_wire ? ddb2 oc0b enable + oc1a enable + usi_three_wire oc0a enable + oc1a enable + (usi_two_wire ? ddb0) pvov 0 oc0b + oc1a + do oc0a + oc1a ptoe usitc 0 0 dieoe pcint2 ? pcie + adc1d + usisie pcint1 ? pcie + ain1d pcint0 ? pcie + ain0d + usisie dieov adc1d ain1d ain0d di t0/usck/scl/int0/ pcint2 input pcint1 input di/sda/pcint0 input aio adc1 input analog comparator negative input analog comparator positive input 66 2586n?avr?04/11 attiny25/45/85 10.4 register description 10.4.1 mcucr ? mcu control register ? bit 6 ? pud: pull-up disable when this bit is written to one, the pull-ups in the i/o ports are disabled even if the ddxn and portxn registers are configured to enable the pull-ups ({ddxn, portxn} = 0b01). see ?con- figuring the pin? on page 56 for more details about this feature. 10.4.2 portb ? port b data register 10.4.3 ddrb ? port b data direction register 10.4.4 pinb ? port b input pins address bit 7 6 5 4 3 2 1 0 0x35 bods pud se sm1 sm0 bodse isc01 isc00 mcucr read/write r r/w r/w r/w r/w r r/w r/w initial value 0 0 0 0 0 0 0 0 bit 76543210 0x18 ? ? portb5 portb4 portb3 portb2 portb1 portb0 portb read/write r r r/w r/w r/w r/w r/w r/w initial value00000000 bit 76543210 0x17 ? ? ddb5 ddb4 ddb3 ddb2 ddb1 ddb0 ddrb read/write r r r/w r/w r/w r/w r/w r/w initial value00000000 bit 76543210 0x16 ? ? pinb5 pinb4 pinb3 pinb2 pinb1 pinb0 pinb read/write r r r/w r/w r/w r/w r/w r/w initial value 0 0 n/a n/a n/a n/a n/a n/a 67 2586n?avr?04/11 attiny25/45/85 11. 8-bit timer/counter0 with pwm 11.1 features ? two independent output compare units ? double buffered outp ut compare registers ? clear timer on compare match (auto reload) ? glitch free, phase correct pulse width modulator (pwm) ? variable pwm period ? frequency generator ? three independent interrupt sources (tov0, ocf0a, and ocf0b) 11.2 overview timer/counter0 is a general purpose 8-bit time r/counter module, with two independent output compare units, and with pwm support. it allows accurate program execution timing (event man- agement) and wave generation. a simplified block diagram of the 8-bit timer/counter is shown in figure 11-1 . for the actual placement of i/o pins, refer to ?pinout attiny25/45/85? on page 2 . cpu accessible i/o registers, including i/o bits and i/o pins, are shown in bold. the device-specific i/o register and bit loca- tions are listed in the ?register description? on page 80 . figure 11-1. 8-bit timer/counter block diagram clock select timer/counter data bus ocrna ocrnb = = tcntn waveform generation waveform generation ocna ocnb = fixed top value control logic = 0 top bottom count clear direction tovn (int.req.) ocna (int.req.) ocnb (int.req.) tccrna tccrnb tn edge detector ( from prescaler ) clk tn 68 2586n?avr?04/11 attiny25/45/85 11.2.1 registers the timer/counter (tcnt0) and output compare registers (ocr0a and ocr0b) are 8-bit registers. interrupt request (abbreviated to int.req . in the figure) signals are all visible in the timer interrupt flag register (tif r). all interrupts are individually masked with the timer inter- rupt mask register (timsk). tifr and timsk are not shown in the figure. the timer/counter can be clocked internally, via the prescaler, or by an external clock source on the t0 pin. the clock select logic block controls which clock source and edge the timer/counter uses to increment (or decrement) its value. the timer/counter is inactive when no clock source is selected. the output from the clock select logic is referred to as the timer clock (clk t0 ). the double buffered output compare registers (ocr0a and ocr0b) is compared with the timer/counter value at all times. the result of the compare can be used by the waveform gen- erator to generate a pwm or variable frequency output on the output compare pins (oc0a and oc0b). see ?output compare unit? on page 71. for details. the comp are match event will also set the compare flag (ocf0a or ocf0b) which can be used to generate an output compare interrupt request. 11.2.2 definitions many register and bit references in this section are written in general form. a lower case ?n? replaces the timer/counter number, in this case 0. a lower case ?x? replaces the output com- pare unit, in this case compare unit a or compare unit b. howe ver, when using the register or bit defines in a program, the precise form must be used, i.e., tcnt0 for accessing timer/counter0 counter value and so on. the definitions in table 11-1 are also used extensively throughout the document. 11.3 timer/counter0 prescal er and clock sources the timer/counter can be clocked by an internal or an external clock source. the clock source is selected by the clock select logic which is contro lled by the clock select (c) bits located in the timer/counter0 contro l register (tccr0b). 11.3.1 internal clock source with prescaler timer/counter0 can be clocked directly by th e system clock (by setting the cs0[2:0] = 1). this provides the fastest operation, with a maximum timer/counter clock frequency equal to system clock frequency (f clk_i/o ). alternatively, one of four taps from the prescaler can be used as a clock source. the prescaled clock has a frequency of either f clk_i/o /8, f clk_i/o /64, f clk_i/o /256, or f clk_i/o /1024. 11.3.2 prescaler reset the prescaler is free running, i.e. it operat es independently of the clock select logic of timer/counter0. since the prescaler is not affected by the timer/counter?s clock select, the state table 11-1. definitions constant description bottom the counter reaches bottom when it becomes 0x00 max the counter reaches its maximum when it becomes 0xff (decimal 255) top the counter reaches the top when it become s equal to the highest value in the count sequence. the top value can be assigned to be the fixed value 0xff (max) or the value stored in the ocr0a register. the assi gnment depends on the mode of operation 69 2586n?avr?04/11 attiny25/45/85 of the prescaler will have implicati ons for situations w here a prescaled clock is used. one exam- ple of a prescaling artifact is when the timer/counter is enabled and clocked by the prescaler (6 > cs0[2:0] > 1). the number of system clock cycl es from when the timer is enabled to the first count occurs can be from 1 to n+1 system clock cycles, where n equals the prescaler divisor (8, 64, 256, or 1024). it is possible to use the prescaler reset for synchronizing the timer/counter to program execution. 11.3.3 external clock source an external clock source applied to the t0 pin can be used as timer/counter clock (clk t0 ). the t0 pin is sampled once every system clock cycle by the pin synchronization logic. the synchro- nized (sampled) signal is then passed through the edge detector. figure 11-2 shows a functional equivalent block diagram of the t0 synchronizati on and edge detector logic. the registers are clocked at the positive edge of the internal system clock ( clk i/o ). the latch is transparent in the high period of the internal system clock. the edge detector generates one clk t 0 pulse for each positive (cs0[2:0] = 7) or negative (cs0[2:0] = 6) edge it detects. figure 11-2. t0 pin sampling the synchronization and e dge detector logic introduces a de lay of 2.5 to 3.5 system clock cycles from an edge has been applied to the t0 pin to the counter is updated. enabling and disabling of the clock input must be done when t0 has been stable for at least one system clock cycle, otherwise it is a risk that a false timer/counter clock pulse is generated. each half period of the external clock applie d must be longer than one system clock cycle to ensure correct sampling. the external clock must be guaranteed to have less than half the sys- tem clock frequency (f extclk < f clk_i/o /2) given a 50/50% duty cycle. since the edge detector uses sampling, the maximum frequency of an external clock it can detect is half the sampling fre- quency (following the nyquist sampling theorem). however, due to variat ion of the system clock frequency and duty cycle caused by oscillator source (crystal, resonator, and capacitors) toler- ances, it is recommended that maximum frequency of an external clock source is less than f clk_i/o /2.5. an external clock source can not be prescaled. tn_sync (to clock select logic) edge detector synchronization dq dq le dq tn clk i/o 70 2586n?avr?04/11 attiny25/45/85 figure 11-3. timer/counter0 prescaler the synchronization logic on the input pins (t0) in figure 11-3 is shown in figure 11-2 on page 69 . 11.4 counter unit the main part of the 8-bit timer/counter is the programmable bi-directional counter unit. figure 11-4 shows a block diagram of the counter and its surroundings. figure 11-4. counter unit block diagram signal description (internal signals): count increment or decrement tcnt0 by 1. direction select between increment and decrement. clear clear tcnt0 (set all bits to zero). clk t n timer/counter clock, referred to as clk t0 in the following. top signalize that tcnt0 has reached maximum value. bottom signalize that tcnt0 has re ached minimum value (zero). psr10 clear clk t0 t0 clk i/o synchronization data b u s tcntn control logic count tovn (int.req.) clock select top tn edge detector ( from prescaler ) clk tn bottom direction clear 71 2586n?avr?04/11 attiny25/45/85 depending of the mode of operation used, the counter is cleared, incremented, or decremented at each timer clock (clk t0 ). clk t0 can be generated from an external or internal clock source, selected by the clock select bits (cs0[2:0]). when no clock source is selected (cs0[2:0] = 0) the timer is stopped. however, the tcnt0 value can be accessed by the cpu, regardless of whether clk t0 is present or not. a cpu write overrides (has priority over) all counter clear or count operations. the counting sequence is determined by the setting of the wgm01 and wgm00 bits located in the timer/counter control register (tccr0a) and the wgm02 bit located in the timer/counter control register b (tccr0b). there are clos e connections between how the counter behaves (counts) and how waveforms are generated on the output compare output oc0a. for more details about advanced counting sequences and waveform generation, see ?modes of opera- tion? on page 73 . the timer/counter overflow flag (tov0) is set according to the mode of operation selected by the wgm0[1:0] bits. tov0 can be used for generating a cpu interrupt. 11.5 output compare unit the 8-bit comparator continuously compares tcnt0 with the output compare registers (ocr0a and ocr0b). whenever tcnt0 equals ocr0a or ocr0b, the comparator signals a match. a match will set the output compare flag (ocf0a or ocf0 b) at the next timer clock cycle. if the corresponding interrupt is enabled, the output compare flag generates an output compare interrupt. the output compare flag is automatically cleared when the interrupt is exe- cuted. alternatively, the flag can be cleared by software by writing a logical one to its i/o bit location. the waveform generator uses the matc h signal to generate an output according to operating mode set by the wgm0[2:0] bits and compare output mode (com0x[1:0]) bits. the max and bottom signals are used by the waveform generator for handling the special cases of the extreme values in some modes of operation ( see ?modes of operation? on page 73. ). figure 11-5 shows a block diagram of the output compare unit. figure 11-5. output compare unit, block diagram ocfnx (int .req.) = (8-bit comparat or ) ocrnx ocnx data bus tcntn wgmn[1:0] wav ef o r m gen er at o r top focn comnx[1:0] bottom 72 2586n?avr?04/11 attiny25/45/85 the ocr0x registers are double buffered when using any of the pulse width modulation (pwm) modes. for the normal and clear timer on compare (ctc) modes of operation, the dou- ble buffering is disabled. the double buffering synchronizes the update of the ocr0x compare registers to either top or bottom of the counting sequence. the synchronization prevents the occurrence of odd-length, non-symmetrical pwm pulses, thereby making the output glitch-free. the ocr0x register access may seem complex, but this is not case. when the double buffering is enabled, the cpu has access to the ocr0x buffer register, and if double buffering is dis- abled the cpu will access the ocr0x directly. 11.5.1 force output compare in non-pwm waveform generation modes, the match output of the comparator can be forced by writing a one to the force outp ut compare (foc0x) bit. forcin g compare match will not set the ocf0x flag or reload/clear the timer, but the oc0x pin will be updated as if a real compare match had occurred (the com0x[1:0] bits settings define whether the oc0x pin is set, cleared or toggled). 11.5.2 compare match bloc king by tcnt0 write all cpu write operations to the tcnt0 register will block any compare ma tch that occur in the next timer clock cycle, even when the timer is stopped. this feature allows ocr0x to be initial- ized to the same value as tcnt0 without triggering an interrupt when the timer/counter clock is enabled. 11.5.3 using the output compare unit since writing tcnt0 in any mo de of operation will block all compare matches for one timer clock cycle, there are risks involved when ch anging tcnt0 when using the output compare unit, independently of whether the timer/counter is running or not. if the value written to tcnt0 equals the ocr0x value, the compare match will be missed, resulting in incorrect waveform generation. similarly, do not write the tcnt0 value equal to bottom when the counter is down-counting. the setup of the oc0x should be performed before setting the data direction register for the port pin to output. the easiest way of setting the oc0x value is to use the force output com- pare (foc0x) strobe bits in normal mode. the oc0x registers keep their values even when changing between waveform generation modes. be aware that the com0x[1:0] bits are not double buffered together with the compare value. changing the com0x[1:0] bits will take effect immediately. 11.6 compare match output unit the compare output mode (com0x[1:0]) bits have two functions. the waveform generator uses the com0x[1:0] bits for defining the output compare (oc0x) state at the next compare match. also, the com0x[1:0] bits control the oc0x pin output source. figure 11-6 shows a sim- plified schematic of the logic affected by the com0x[1:0] bit setting. the i/o registers, i/o bits, and i/o pins in the figure are shown in bold. only the parts of the general i/o port control regis- ters (ddr and port) that are affected by the com0x[1:0] bits are shown. when referring to the oc0x state, the reference is for the internal oc0x register, not the oc0x pin. if a system reset occur, the oc0x register is reset to ?0?. 73 2586n?avr?04/11 attiny25/45/85 figure 11-6. compare match output unit, schematic the general i/o port function is overridden by the output compare (oc0x) from the waveform generator if either of the com0x[1:0] bits are set. however, the oc0x pin direction (input or out- put) is still controlled by the da ta direction register (ddr) for th e port pin. the data direction register bit for the oc0x pin (ddr_oc0x) must be set as output before the oc0x value is visi- ble on the pin. the port override function is independent of the waveform generation mode. the design of the output compare pin logic allows initialization of the oc0x state before the out- put is enabled. note that some com0x[1:0] bit settings are reserved for certain modes of operation. see ?register description? on page 80. 11.6.1 compare output mode and waveform generation the waveform generator uses the com0x[1:0] bits differently in normal, ctc, and pwm modes. for all modes, setting the com0x[1:0] = 0 tells the waveform generator that no action on the oc0x register is to be performed on the next compare match. for compare output actions in the non-pwm modes refer to table 11-2 on page 80 . for fast pwm mode, refer to table 11-3 on page 81 , and for phase correct pwm refer to table 11-4 on page 81 . a change of the com0x[1:0] bits state will have effect at the first compare match after the bits are written. for non-pwm modes, the action can be forced to have immediate effect by using the foc0x strobe bits. 11.7 modes of operation the mode of operation, i.e., the behavior of the timer/counter and the output compare pins, is defined by the combination of the waveform generation mode (wgm0[2:0]) and compare out- put mode (com0x[1:0]) bits. the compare output mode bits do not affect the counting port ddr dq dq ocn pin ocnx dq waveform generator comnx1 comnx0 0 1 data b u s focn clk i/o 74 2586n?avr?04/11 attiny25/45/85 sequence, while the waveform generation mode bits do. the com0x[1:0] bits control whether the pwm output generated should be inverted or not (inverted or non-inverted pwm). for non- pwm modes the com0x[1:0] bits control whether the output should be set, cleared, or toggled at a compare match ( see ?compare match output unit? on page 72. ). for detailed timing information refer to figure 11-10 , figure 11-11 , figure 11-12 and figure 11- 13 in ?timer/counter timing diagrams? on page 78 . 11.7.1 normal mode the simplest mode of operation is the normal mode (wgm0[2:0] = 0). in this mode the counting direction is always up (incrementing), and no counter clear is performed. the counter simply overruns when it passes its maximum 8-bit value (top = 0xff) and then restarts from the bot- tom (0x00). in normal o peration the timer/counter overflow flag (tov0) will be set in the same timer clock cycle as the tcnt0 becomes zero. the tov0 flag in this case behaves like a ninth bit, except that it is only set, not cleared. however, combined with the timer overflow interrupt that automatically clears the tov0 flag, the timer resolution can be increased by software. there are no special cases to consider in the normal mode, a new counter value can be written anytime. the output compare unit can be used to generate interrupts at some given time. using the out- put compare to generate waveforms in normal mode is not recommended, since this will occupy too much of the cpu time. 11.7.2 clear timer on compare match (ctc) mode in clear timer on compare or ctc mode (wgm0[2:0] = 2), the ocr0a register is used to manipulate the counter resolution. in ctc mode the counter is cleared to zero when the counter value (tcnt0) matches the ocr0a. the ocr0a defines the top value for the counter, hence also its resolution. this mode allows greater control of the compare match output frequency. it also simplifies the operation of counting external events. the timing diagram for the ctc mode is shown in figure 11-7 . the counter value (tcnt0) increases until a compare match occurs between tcnt0 and ocr0a, and then counter (tcnt0) is cleared. figure 11-7. ctc mode, timing diagram an interrupt can be generated each time the counter value reaches the top value by using the ocf0a flag. if the interrupt is enabled, the interrupt handler routine can be used for updating the top value. however, changing top to a va lue close to bottom when the counter is run- tcntn ocn (toggle) ocnx int errup t fl ag set 1 4 pe r i o d 2 3 (comnx[1:0] = 1) 75 2586n?avr?04/11 attiny25/45/85 ning with none or a low prescaler value must be done with care since the ctc mode does not have the double buffering feature. if the new value written to ocr0a is lower than the current value of tcnt0, the counter will miss the compar e match. the counter will then have to count to its maximum value (0xff) and wrap around starting at 0x00 before the compare match can occur. for generating a waveform output in ctc mode, the oc0a output can be set to toggle its logical level on each compare match by setting the compare output mode bits to toggle mode (com0a[1:0] = 1). the oc0a value will not be visible on the port pin unless the data direction for the pin is set to output. the waveform generated will have a maximum frequency of f oc0 = f clk_i/o /2 when ocr0a is set to zero (0x00). the waveform frequency is defined by the following equation: the n variable represents the prescale factor (1, 8, 64, 256, or 1024). as for the normal mode of operation, the tov0 flag is set in the same timer clock cycle that the counter counts from max to 0x00. 11.7.3 fast pwm mode the fast pulse width modulation or fast pwm mode (wgm0[2:0] = 3 or 7) provides a high fre- quency pwm waveform generation option. the fast pwm differs from the other pwm option by its single-slope operation. the counter counts from bottom to top then restarts from bot- tom. top is defined as 0xff when wgm0[2:0] = 3, and ocr0a when wgm0[2:0] = 7. in non-inverting compare output mode, the output compare (oc0x) is cleared on the compare match between tcnt0 and ocr0x, and set at bottom. in inverting compare output mode, the output is set on compare match and cleared at bottom. due to the single-slope operation, the operatin g frequency of the fast pwm mode can be twice as high as the phase correct pwm mode that use dual-slope operation. this high frequency makes the fast pwm mode well suited for power regulation, rectification, and dac applications. high frequency allows physically small sized external components (coils, capacitors), and there- fore reduces total system cost. in fast pwm mode, the counter is incremented until the counter value matches the top value. the counter is then cleared at the following timer clock cycle. the timing diagram for the fast pwm mode is shown in figure 11-8 . the tcnt0 value is in the timing diagram shown as a his- togram for illustrating the single-slope operation. the diagram includes non-inverted and inverted pwm outputs. the small horizontal li ne marks on the tcnt0 slopes represent com- pare matches between ocr0x and tcnt0. f ocnx f clk_i/o 2 n 1 ocrnx + () ?? -------------------------------------------------- = 76 2586n?avr?04/11 attiny25/45/85 figure 11-8. fast pwm mode, timing diagram the timer/counter overflow flag (tov0) is set each time the counter reaches top. if the inter- rupt is enabled, the interrupt handler routine can be used for updating the compare value. in fast pwm mode, the compare unit allows generation of pwm waveforms on the oc0x pins. setting the com0x[1:0] bits to two will produce a non-inverted pwm and an inverted pwm out- put can be generated by setting the com0x[1:0] to three: setting the com0a[1:0] bits to one allowes the ac0a pin to toggle on compare matches if the wgm02 bit is set. this option is not available for the oc0b pin (see table 11-3 on page 81 ). the actual oc0x value will only be vis- ible on the port pin if the data direction for the port pin is set as output. the pwm waveform is generated by setting (or clearing) the oc0x register at the compare match between ocr0x and tcnt0, and clearing (or setting) the oc0x register at the timer clock cycle the counter is cleared (changes from top to bottom). the pwm frequency for the output can be calculated by the following equation: the n variable represents the prescale factor (1, 8, 64, 256, or 1024). the extreme values for the ocr0a register represents special cases when generating a pwm waveform output in the fast pwm mode. if the ocr0a is set equal to bottom, the output will be a narrow spike for each max+1 timer clock cycle. setting the ocr0a equal to max will result in a constantly high or low output (depending on the polarity of the output set by the com0a[1:0] bits.) a frequency (with 50% duty cycle) waveform output in fast pwm mode can be achieved by set- ting oc0x to toggle its logical level on ea ch compare match (com0x[1:0] = 1). the waveform generated will have a maximum frequency of f oc0 = f clk_i/o /2 when ocr0a is set to zero. this feature is similar to the oc0a toggle in ctc mode, except the double buffer feature of the out- put compare unit is enabled in the fast pwm mode. tcntn ocrnx up dat e and tovn i n t er r u p t fl ag set 1 pe r i o d 2 3 ocn ocn (comnx[1:0] = 2) (comnx[1:0] = 3) ocrnx int errup t fl ag set 4 5 6 7 f ocnxpwm f clk_i/o n 256 ? ------------------ = 77 2586n?avr?04/11 attiny25/45/85 11.7.4 phase correct pwm mode the phase correct pwm mode (wgm0[2:0] = 1 or 5) provides a high resolution phase correct pwm waveform generation option. the phase correct pwm mode is based on a dual-slope operation. the counter counts repeatedly from bottom to top and then from top to bot- tom. top is defined as 0xff when wgm0[2:0] = 1, and ocr0a when wgm0[2:0] = 5. in non- inverting compare output mode, the output compare (oc0x) is cleared on the compare match between tcnt0 and ocr0x while upcounting, and set on the compare match while down- counting. in inverting output compare mode, the operation is inverted. the dual-slope operation has lower maximum operation frequency than single slope operation. however, due to the sym- metric feature of the dual-slope pwm modes, these modes are preferred for motor control applications. in phase correct pwm mode the counter is incremented until the counter value matches top. when the counter reaches top, it changes the count direction. the tcnt0 value will be equal to top for one timer clock cycle. the timing diagram for the phase correct pwm mode is shown on figure 11-9 . the tcnt0 value is in the timing diagram shown as a histogram for illustrating the dual-slope operation. the diagram includes non-inverted and inverted pwm outputs. the small horizontal line marks on the tcnt0 slop es represent compare matches between ocr0x and tcnt0. figure 11-9. phase correct pwm mode, timing diagram the timer/counter overflow flag (tov0) is set each time the counter reaches bottom. the interrupt flag can be used to generate an interrupt each time the counter reaches the bottom value. in phase correct pwm mode, the compare unit allows generation of pwm waveforms on the oc0x pins. setting the com0x[1:0] bits to tw o will produce a non-inverted pwm. an inverted pwm output can be generated by setting the com0x[1:0] to three: setting the com0a0 bits to one allows the oc0a pin to toggle on compare ma tches if the wgm02 bit is set. this option is tovn interrupt flag set ocnx interrupt flag set 1 2 3 tcntn period ocn ocn (comnx[1:0] = 2) (comnx[1:0] = 3) ocrnx update 78 2586n?avr?04/11 attiny25/45/85 not available for the oc0b pin (see table 11-4 on page 81 ). the actual oc0x value will only be visible on the port pin if the data direction for th e port pin is set as output. the pwm waveform is generated by clearing (or setting) the oc0x register at the compare match between ocr0x and tcnt0 when the counter increments, and setti ng (or clearing) the oc0x register at com- pare match between ocr0x and tcnt0 when the counter decrements. the pwm frequency for the output when using phase correct pwm can be calculated by the following equation: the n variable represents the prescale factor (1, 8, 64, 256, or 1024). the extreme values for the ocr0a register represent special cases when generating a pwm waveform output in the phase correct pwm mode. if the ocr0a is set equal to bottom, the output will be continuously low an d if set equal to max the output will be continuously high for non-inverted pwm mode. for in verted pwm the output will have the opposite logic values. at the very start of period 2 in figure 11-9 ocn has a transition from high to low even though there is no compare match. the point of this transition is to guaratee symmetry around bot- tom. there are two cases that give a transition without compare match, as follows: ? ocr0a changes its value from max, like in figure 11-9 . when the ocr0a value is max the ocn pin value is the same as the result of a down-counting compare match. to ensure symmetry around bottom the ocn value at max must correspond to the result of an up- counting compare match. ? the timer starts counting from a value higher than the one in ocr0a, and for that reason misses the compare match and hence the ocn change that would have happened on the way up. 11.8 timer/counter timing diagrams the timer/counter is a synchronous design and the timer clock (clk t0 ) is therefore shown as a clock enable signal in the following figures. the figures include information on when interrupt flags are set. figure 11-10 contains timing data for basic timer/counter operation. the figure shows the count sequence close to the max val ue in all modes other than phase correct pwm mode. figure 11-10. timer/counter timing diagram, no prescaling figure 11-11 shows the same timing data, but with the prescaler enabled. f ocnxpcpwm f clk_i/o n510 ? ------------------ = clk tn (clk i/o /1) tovn clk i/o tcntn max - 1 max bottom bottom + 1 79 2586n?avr?04/11 attiny25/45/85 figure 11-11. timer/counter timing dia gram, with prescaler (f clk_i/o /8) figure 11-12 shows the setting of ocf0b in all modes and ocf0a in all modes except ctc mode and pwm mode, where ocr0a is top. figure 11-12. timer/counter timing diagram, setting of ocf0x, with prescaler (f clk_i/o /8) figure 11-13 shows the setting of ocf0a and the clearing of tcnt0 in ctc mode and fast pwm mode where ocr0a is top. figure 11-13. timer/counter timing diagram, clear timer on compare match mode, with pres- caler (f clk_i/o /8) tovn tcntn max - 1 max bottom bottom + 1 clk i/o clk tn (clk i/o /8) ocfnx ocrnx tcntn ocrnx value ocrnx - 1 ocrnx ocrnx + 1 ocrnx + 2 clk i/o clk tn (clk i/o /8) ocfnx ocrnx tcntn (ctc) top top - 1 top bottom bottom + 1 clk i/o clk tn (clk i/o /8) 80 2586n?avr?04/11 attiny25/45/85 11.9 register description 11.9.1 gtccr ? general timer/counter control register ? bit 7 ? tsm: timer/counter synchronization mode writing the tsm bit to one activates the timer/counter synchronization mode. in this mode, the value written to psr0 is kept, hence keeping the prescaler reset signal asserted. this ensures that the timer/counter is halted and can be conf igured without the risk of advancing during con- figuration. when the tsm bit is written to zero, the psr0 bit is cleared by hardware, and the timer/counter start counting. ? bit 0 ? psr0: prescaler reset timer/counter0 when this bit is one, the timer/counter0 prescale r will be reset. this bit is normally cleared immediately by hardware, except if the tsm bit is set. 11.9.2 tccr0a ? timer/counter control register a ? bits 7:6 ? com0a[1:0]: compare match output a mode ? bits 5:4 ? com0b[1:0]: compare match output b mode the com0a[1:0] and com0b[1:0] bits control the behaviour of output compare pins oc0a and oc0b, respectively. if any of the com0a[1:0] bits are set, the oc0a output overrides the normal port functionality of the i/o pin it is connected to. similarly, if any of the com0b[1:0] bits are set, the oc0b output overrides the normal port functi onality of the i/o pin it is connected to. how- ever, note that the data direction register (d dr) bit corresponding to the oc0a and oc0b pins must be set in order to enable the output driver. when oc0a/oc0b is connected to the i/o pin, the function of the com0a[1:0]/com0b[1:0] bits depend on the wgm0[2:0] bit setting. table 11-2 shows the com0x[1:0] bit functionality when the wgm0[2:0] bits are set to a normal or ctc mode (non-pwm). bit 7 6 5 4 3 2 1 0 0x2c tsm pwm1b com1b1 com1b0 foc1b foc1a psr1 psr0 gtccr read/write r/w r r r r r r r/w initial value 0 0 0 0 0 0 0 0 bit 7 6 5 4 3 210 0x2a com0a 1 com0a 0 com0b 1 com0b 0 ?? wgm01 wgm00 tccr0a read/write r/w r/w r/w r/w r r r/w r/w initial value 0 0 0 0 0 0 0 0 table 11-2. compare output mode, non-pwm mode com0a1 com0b1 com0a0 com0b0 description 0 0 normal port operation, oc0a/oc0b disconnected. 0 1 toggle oc0a/oc0b on compare match 1 0 clear oc0a/oc0b on compare match 1 1 set oc0a/oc0b on compare match 81 2586n?avr?04/11 attiny25/45/85 table 11-3 shows the com0x[1:0] bit functionality when the wgm0[2:0] bits are set to fast pwm mode. note: 1. a special case occurs when ocr0a or o cr0b equals top and com0a1/com0b1 is set. in this case, the compare match is ignored, bu t the set or clear is done at bottom. see ?fast pwm mode? on page 75 for more details. table 11-4 shows the com0x[1:0] bit functionality when the wgm0[2:0] bits are set to phase correct pwm mode. note: 1. a special case occurs when ocr0a or o cr0b equals top and com0a1/com0b1 is set. in this case, the compare match is ignored, but the set or clear is done at top. see ?phase cor- rect pwm mode? on page 77 for more details. ? bits 3:2 ? res: reserved bits these bits are reserved bits in the attiny25/45/85 and will always read as zero. ? bits 1:0 ? wgm0[1:0]: waveform generation mode combined with the wgm02 bit found in the tccr0b register, these bits control the counting sequence of the counter, the source for maximum (top) counter value, and what type of wave- form generation to be used, see table 11-5 . modes of operation supported by the timer/counter table 11-3. compare output mode, fast pwm mode (1) com0a1 com0b1 com0a0 com0b0 description 0 0 normal port operation, oc0a/oc0b disconnected. 01reserved 10 clear oc0a/oc0b on compare match, set oc0a/oc0b at bottom (non-inverting mode) 11 set oc0a/oc0b on compare match, clear oc0a/oc0b at bottom (inverting mode) table 11-4. compare output mode, phase correct pwm mode (1) com0a1 com0b1 com0a0 com0b0 description 0 0 normal port operation, oc0a/oc0b disconnected. 01reserved 10 clear oc0a/oc0b on compare match when up-counting. set oc0a/oc0b on compare match when down-counting. 11 set oc0a/oc0b on compare match when up-counting. clear oc0a/oc0b on compare match when down-counting. 82 2586n?avr?04/11 attiny25/45/85 unit are: normal mode (counter), clear timer on compare match (ctc) mode, and two types of pulse width modulation (pwm) modes (see ?modes of operation? on page 73 ). notes: 1. max = 0xff 2. bottom = 0x00 11.9.3 tccr0b ? timer/counter control register b ? bit 7 ? foc0a: force output compare a the foc0a bit is only active when the wgm bits specify a non-pwm mode. however, for ensuring compatibility with future devices, this bit must be set to zero when tccr0b is written when operating in pwm mode. when writing a logical one to the foc0a bit, an immediate compare match is forced on the waveform generation unit. the oc0a output is changed according to its com0a[1:0] bits setting. note that the foc0a bit is implemented as a strobe. therefore it is the value present in the com0a[1:0] bits that determines the effect of the forced compare. a foc0a strobe will not generate any interrupt, nor will it clear the timer in ctc mode using ocr0a as top. the foc0a bit is always read as zero. ? bit 6 ? foc0b: force output compare b the foc0b bit is only active when the wgm bits specify a non-pwm mode. however, for ensuring compatibility with future devices, this bit must be set to zero when tccr0b is written when operating in pwm mode. when writing a logical one to the foc0b bit, an immediate compare match is forced on the waveform generation unit. the oc0b output is changed according to its com0b[1:0] bits setting. note that the foc0b bit is implemented as a strobe. therefore it is the value present in the com0b[1:0] bits that determines the effect of the forced compare. table 11-5. waveform generation mode bit description mode wgm 02 wgm 01 wgm 00 timer/counter mode of operation top update of ocrx at tov flag set on 0 0 0 0 normal 0xff immediate max (1) 1 0 0 1 pwm, phase correct 0xff top bottom (2) 2 0 1 0 ctc ocra immediate max (1) 3 0 1 1 fast pwm 0xff bottom (2) max (1) 4 1 0 0 reserved ? ? ? 5 1 0 1 pwm, phase correct ocra top bottom (2) 6 1 1 0 reserved ? ? ? 7 1 1 1 fast pwm ocra bottom (2) top bit 7 6 5 4 3 2 1 0 0x33 foc0a foc0b ? ? wgm02 cs02 cs01 cs00 tccr0b read/write w w r r r/w r/w r/w r/w initial value 0 0 0 0 0 0 0 0 83 2586n?avr?04/11 attiny25/45/85 a foc0b strobe will not generate any interrupt, nor will it clear the timer in ctc mode using ocr0b as top. the foc0b bit is always read as zero. ? bits 5:4 ? res: reserved bits these bits are reserved bits in the attiny25/45/85 and will always read as zero. ? bit 3 ? wgm02: waveform generation mode see the description in the ?tccr0a ? timer/counter control register a? on page 80 . ? bits 2:0 ? cs0[2:0]: clock select the three clock select bits select the clock source to be used by the timer/counter. if external pin modes are used for the timer/counter0, transitions on the t0 pin will clock the counter even if the pin is configured as an output. this feature allows software control of the counting. 11.9.4 tcnt0 ? timer/counter register the timer/counter register gives direct ac cess, both for read and write operations, to the timer/counter unit 8-bit counter. writing to the tcnt0 register blocks (removes) the compare match on the following timer clock. modifying the counter (tcnt0) while the counter is running, introduces a risk of missing a compare match between tcnt0 and the ocr0x registers. 11.9.5 ocr0a ? output compare register a the output compare register a contains an 8-bi t value that is continuously compared with the counter value (tcnt0). a match can be used to generate an output compare interrupt, or to generate a waveform output on the oc0a pin. table 11-6. clock select bit description cs02 cs01 cs00 description 0 0 0 no clock source (timer/counter stopped) 001clk i/o /(no prescaling) 010clk i/o /8 (from prescaler) 011clk i/o /64 (from prescaler) 100clk i/o /256 (from prescaler) 101clk i/o /1024 (from prescaler) 1 1 0 external clock source on t0 pin. clock on falling edge. 1 1 1 external clock source on t0 pin. clock on rising edge. bit 76543210 0x32 tcnt0 [7:0] tcnt0 read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value00000000 bit 76543210 0x29 ocr0a [7:0] ocr0a read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value00000000 84 2586n?avr?04/11 attiny25/45/85 11.9.6 ocr0b ? output compare register b the output compare register b contains an 8-bi t value that is continuously compared with the counter value (tcnt0). a match can be used to generate an output compare interrupt, or to generate a waveform output on the oc0b pin. 11.9.7 timsk ? timer/counter interrupt mask register ? bits 7, 0 ? res: reserved bits these bits are reserved bits and will always read as zero. ? bit 4 ? ocie0a: timer/counter0 output compare match a interrupt enable when the ocie0a bit is written to one, and th e i-bit in the status register is set, the timer/counter0 compare match a interrupt is enabled. the corresponding interrupt is executed if a compare match in timer/counter0 occurs, i.e., when the ocf0a bit is set in the timer/counter 0 interrupt flag register ? tifr0. ? bit 3 ? ocie0b: timer/counter output compare match b interrupt enable when the ocie0b bit is written to one, and the i-bit in the status register is set, the timer/counter compare match b interrupt is enab led. the corresponding interrupt is executed if a compare match in timer/counter occurs, i.e., when the ocf0b bit is set in the timer/counter interrupt flag register ? tifr0. ? bit 1 ? toie0: timer/counter0 overflow interrupt enable when the toie0 bit is written to one, and the i-bit in the status register is set, the timer/counter0 overflow interrupt is enabled. the corresponding interrupt is executed if an overflow in timer/counter0 occurs, i.e., when the tov0 bit is set in the timer/counter 0 inter- rupt flag register ? tifr0. 11.9.8 tifr ? timer/counter interrupt flag register ? bits 7, 0 ? res: reserved bits these bits are reserved bits and will always read as zero. ? bit 4 ? ocf0a: output compare flag 0 a the ocf0a bit is set when a compare match occurs between the timer/counter0 and the data in ocr0a ? output compare register0. ocf0a is cleared by hardware when executing the cor- responding interrupt handling vector. alternativel y, ocf0a is cleared by writing a logic one to bit 76543210 0x28 ocr0b [7:0] ocr0b read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value00000000 bit 76543 2 10 0x39 ? ocie1a ocie1b ocie0a ocie0b toie1 toie0 ? timsk read/write r r/w r/w r/w r/w r/w r/w r initial value 0 0 0 0 0 0 0 0 bit 76543210 0x38 ? ocf1a ocf1b ocf0a ocf0b tov1 tov0 ?tifr read/write r r/w r/w r/w r/w r/w r/w r initial value00000000 85 2586n?avr?04/11 attiny25/45/85 the flag. when the i-bit in sreg, ocie0a (timer/counter0 compare match interrupt enable), and ocf0a are set, the timer/counter0 compare match interrupt is executed. ? bit 3 ? ocf0b: output compare flag 0 b the ocf0b bit is set when a compare match occurs between the timer/counter and the data in ocr0b ? output compare register0 b. ocf0b is cleared by hardware when executing the cor- responding interrupt handling vector. alternatively, ocf0b is cleared by writing a logic one to the flag. when the i-bit in sreg, ocie0b (timer/counter compare b match interrupt enable), and ocf0b are set, the timer/counter compare match interrupt is executed. ? bit 1 ? tov0: timer/counter0 overflow flag the bit tov0 is set when an overflow occurs in timer/counter0. tov0 is cleared by hardware when executing the corresponding interrupt handling vector. alternatively, tov0 is cleared by writing a logic one to the flag. when the sreg i-bit, toie0 (timer/counter0 overflow interrupt enable), and tov0 are set, the timer/counter0 overflow interrupt is executed. the setting of this flag is dependent of the wgm0[2:0] bit setting. refer to table 11-5 , ?wave- form generation mode bit description? on page 82 . 86 2586n?avr?04/11 attiny25/45/85 12. 8-bit timer/counter1 the timer/counter 1 is a general purpose 8-bit timer/counter module that has a separate pres- caling selection from the separate prescaler. 12.1 timer/counter1 prescaler figure 12-1 shows the timer/counter1 prescaler that supports two clocking modes, a synchro- nous clocking mode and an asynchronous clocking mode. the synchronous clocking mode uses the system clock (ck) as the cl ock timebase and asyn chronous mode uses the fast peripheral clock (pck) as the clock time base. the pcke bi t from the pllcsr register enables the asyn- chronous mode when it is set (?1?). figure 12-1. timer/counter1 prescaler in the asynchronous clocking mode the clock se lections are from pck to pck/16384 and stop, and in the synchronous clocking mode the clock selections are from ck to ck/16384 and stop. the clock options are described in table 12-5 on page 92 and the timer/counter1 control reg- ister, tccr1. setting the psr1 bit in gtccr register resets the prescaler. the pcke bit in the pllcsr register enables the asynchronous mode. the frequency of the fast peripheral clock is 64 mhz (or 32 mhz in low speed mode). 12.2 counter and compare units the timer/counter1 general operation is described in the asynchronous mode and the opera- tion in the synchronous mode is mentioned only if there are differences between these two modes. figure 12-2 shows timer/counter 1 synchronizati on register block diagram and syn- chronization delays in between registers. note that all clock gating details are not shown in the figure. the timer/counter1 register values go through the internal synchronization registers, which cause the input synchronization delay, before affecting the counter operation. the regis- ters tccr1, gtccr, ocr1a, ocr1b, and ocr1c can be read back right after writing the register. the read back values are delayed for the timer/counter1 (tcnt1) register and flags (ocf1a, ocf1b, and tov1), because of the input and output synchronization. the timer/counter1 features a high resolution and a high accuracy usage with the lower pres- caling opportunities. it can also support two accurate, high speed, 8-bit pulse width modulators using clock speeds up to 64 mhz (or 32 mhz in low speed mode). in this mode, timer/counter1 count enable p s r1 c s 10 c s 11 c s 12 pck 64/ 3 2 mhz 0 c s 1 3 14-bit t/c pre s caler t1ck/2 t1ck t1ck/4 t1ck/ 8 t1ck/16 t1ck/ 3 2 t1ck/64 t1ck/12 8 t1ck/256 t1ck/512 t1ck/1024 t1ck/204 8 t1ck/4096 t1ck/ 8 192 t1ck/16 38 4 ck pcke t1ck 87 2586n?avr?04/11 attiny25/45/85 timer/counter1 and the output compare registers serve as dual stand-alone pwms with non- overlapping non-inverted and inverted outputs. refer to page 89 for a detailed description on this function. similarly, the high prescaling opportunities make this unit useful for lower speed functions or exact timing func tions with infrequent actions. figure 12-2. timer/counter 1 synchronization register block diagram. timer/counter1 and the prescaler allow running the cpu from any clock source while the pres- caler is operating on the fast 64 mhz (or 32 mhz in low speed mode) pck clock in the asynchronous mode. note that the system clock freque ncy must be lower than one th ird of the pck frequency. the synchronization mechanism of the asynchronous timer/counter1 needs at least two edges of the pck when the system clock is high. if the frequency of the system clock is too high, it is a risk that data or control values are lost. the following figure 12-3 shows the block diagram for timer/counter1. 8 -bit databu s ocr1a ocr1a_ s i tcnt_ s o ocr1b ocr1b_ s i ocr1c ocr1c_ s i tccr1 tccr1_ s i gtccr gtccr_ s i tcnt1 tcnt1_ s i ocf1a ocf1a_ s i ocf1b ocf1b_ s i tov1 tov1_ s i tov1_ s o ocf1b_ s o ocf1a_ s o tcnt1 s a s a pcke ck pck io-regi s ter s inp u t s ynchroniz a tion regi s ter s timer/co u nter1 o u tp u t s ynchroniz a tion regi s ter s s ync mode a s ync mode 1 ck del a y ~1 ck del a y 1 pck del a y no del a y tcnt1 ocf1a ocf1b tov1 1/2 ck del a y 1 ck del a y 1/2 ck del a y 1..2 pck del a y 88 2586n?avr?04/11 attiny25/45/85 figure 12-3. timer/counter1 block diagram three status flags (overflow and compare matches) are found in the timer/counter interrupt flag register - tifr. control signals are found in the timer/counter control registers tccr1 and gtccr. the interrupt enable/ disable settings are found in the timer/counter interrupt mask register - timsk. the timer/counter1 contains three output compare registers, ocr1a, ocr1b, and ocr1c as the data source to be compared with the timer/counter1 contents. in normal mode the out- put compare functions are operational with all three output compare registers. ocr1a determines action on the oc1a pin (pb1), and it can generate timer1 oc1a interrupt in normal mode and in pwm mode. likewise, ocr1b determines action on the oc1b pin (pb4) and it can generate timer1 oc1b interrupt in normal mode and in pwm mode. ocr1c holds the timer/counter maximum value, i.e. the clear on compare match value. in the normal mode an overflow interrupt (tov1) is generated when timer/counter1 counts from $ff to $00, while in the pwm mode the overflow interrupt is generated when timer/counter1 counts either from $ff to $00 or from ocr1c to $00. the inverted pwm outputs oc1a and oc1b are not connected in normal mode. in pwm mode, ocr1a and ocr1b provide the da ta values against which the timer counter value is compared. upon compare match the pwm outputs (oc1a, oc1a , oc1b, oc1b ) are generated. in pwm mode, the timer counter counts up to the value specified in the output com- pare register ocr1c and starts again from $00. this feature allows limiting the counter ?full? value to a specified value, lower than $ff. together with the many prescaler options, flexible pwm frequency selection is provided. table 12-3 on page 91 lists clock selection and ocr1c 8-bit databus timer int. flag register (tifr) timer/counter1 8-bit comparator t/c1 output compare register timer int. mask register (timsk) timer/counter1 (tcnt1) t/c clear t/c1 control logic tov1 ocf1b ocf1b tov1 toie0 toie1 ocie1b ocie1a ocf1a ocf1a ck pck t/c1 over- flow irq t/c1 compare match b irq oc1a (pb1) t/c1 compare match a irq t/c control register 1 (tccr1) com1b1 pwm1a pwm1b com1b0 foc1a foc1b (ocr1a) (ocr1b) (ocr1c) 8-bit comparator t/c1 output compare register tov0 com1a1 com1a0 8-bit comparator t/c1 output compare register global t/c control register (gtccr) cs12 psr1 cs11 cs10 cs13 ctc1 oc1a (pb0) oc1b (pb4) oc1b (pb3) dead time generator dead time generator 89 2586n?avr?04/11 attiny25/45/85 values to obtain pwm frequencies from 20 khz to 250 khz in 10 khz steps and from 250 khz to 500 khz in 50 khz steps. higher pwm frequencies can be obtained at the expense of resolution. 12.2.1 timer/counter1 initialization for asynchronous mode to set timer/counter1 in asynchronous mode first enable pll and then wait 100 s for pll to stabilize. next, poll the pl ock bit until it is set and then set the pcke bit. 12.2.2 timer/counter1 in pwm mode when the pwm mode is selected, timer/counter1 and the output compare register c - ocr1c form a dual 8-bit, free-running and glitch-free pwm generator with outputs on the pb1(oc1a) and pb4(oc1b) pins and inverted outputs on pins pb0(oc1a ) and pb3(oc1b ). as default non-overlapping times for complementary output pairs are zero, but they can be inserted using a dead time generator (see description on page 100). figure 12-4. the pwm output pair when the counter value match the contents of ocr1a or ocr1b, the oc1a and oc1b outputs are set or cleared according to the com1a1/com1a0 or com1b1/com1b0 bits in the timer/counter1 control register a - tccr1, as shown in table 12-1 . timer/counter1 acts as an up-counter, counting from $00 up to the value specified in the output compare register ocr1c, and starting from $00 up again. a compare match with oc1c will set an overflow interrupt flag (tov1) after a synchronization delay following the compare event. note that in pwm mode, writing to the output compare registers ocr1a or ocr1b, the data value is first transferred to a temporary location. the value is latched into ocr1a or ocr1b when the timer/counter reaches ocr1c. this prevents the occurrence of odd-length pwm pulses (glitches) in the event of an unsynchronized ocr1a or ocr1b. see figure 12-5 for an example. table 12-1. compare mode select in pwm mode com1x1 com1x0 effect on output compare pins 00 oc1x not connected. oc1x not connected. 01 oc1x cleared on compare match. set whentcnt1 = $00. oc1x set on compare match. cleared when tcnt1 = $00. 10 oc1x cleared on compare match. set when tcnt1 = $00. oc1x not connected. 11 oc1x set on compare match. cleared when tcnt1= $00. oc1x not connected. pwm1x pwm1x x = a or b t non-overlap =0 t non-overlap =0 90 2586n?avr?04/11 attiny25/45/85 figure 12-5. effects of unsynchronized ocr latching during the time between the wr ite and the latch operation, a read from ocr1a or ocr1b will read the contents of the temporary location. this means that the most recently written value always will read out of ocr1a or ocr1b. when ocr1a or ocr1b contain $00 or the top va lue, as specified in ocr1c register, the out- put pb1(oc1a) or pb4(oc1b) is held low or high according to the settings of com1a1/com1a0. this is shown in table 12-2 . in pwm mode, the timer overflow flag - tov1 is set when the tcnt1 counts to the ocr1c value and the tcnt1 is reset to $00. the timer overflow interrupt1 is executed when tov1 is set provided that timer overflow interrupt and glob al interrupts are enabled. this also applies to the timer output compare flags and interrupts. the frequency of the pwm will be timer clock 1 fr equency divided by (ocr1c value + 1). see the following equation: resolution shows how many bits are required to express the value in the ocr1c register and can be calculated using the following equation: table 12-2. pwm outputs ocr1x = $00 or ocr1c, x = a or b com1x1 com1x0 ocr1x output oc1x output oc1x 0 1 $00 l h 0 1 ocr1c h l 1 0 $00 l not connected. 1 0 ocr1c h not connected. 1 1 $00 h not connected. 1 1 ocr1c l not connected. pwm output oc1x pwm output oc1x unsynchronized oc1x latch synchronized oc1x latch counter value compare value counter value compare value compare value changes glitch compare value changes f pwm f tck1 ocr1c + 1 () ----------------------------------- - = 91 2586n?avr?04/11 attiny25/45/85 table 12-3. timer/counter1 clock prescale se lect in the asynchronous mode pwm frequency clock select ion cs1[3:0] ocr1c resolution 20 khz pck/16 0101 199 7.6 30 khz pck/16 0101 132 7.1 40 khz pck/8 0100 199 7.6 50 khz pck/8 0100 159 7.3 60 khz pck/8 0100 132 7.1 70 khz pck/4 0011 228 7.8 80 khz pck/4 0011 199 7.6 90 khz pck/4 0011 177 7.5 100 khz pck/4 0011 159 7.3 110 khz pck/4 0011 144 7.2 120 khz pck/4 0011 132 7.1 130 khz pck/2 0010 245 7.9 140 khz pck/2 0010 228 7.8 150 khz pck/2 0010 212 7.7 160 khz pck/2 0010 199 7.6 170 khz pck/2 0010 187 7.6 180 khz pck/2 0010 177 7.5 190 khz pck/2 0010 167 7.4 200 khz pck/2 0010 159 7.3 250 khz pck 0001 255 8.0 300 khz pck 0001 212 7.7 350 khz pck 0001 182 7.5 400 khz pck 0001 159 7.3 450 khz pck 0001 141 7.1 500 khz pck 0001 127 7.0 r 2ocr1c 1 + () log = 92 2586n?avr?04/11 attiny25/45/85 12.3 register description 12.3.1 tccr1 ? timer/counter1 control register ? bit 7 ? ctc1 : clear timer/counter on compare match when the ctc1 control bit is set (one), timer/counter1 is reset to $00 in the cpu clock cycle after a compare match with ocr1c register value. if the control bit is cleared, timer/counter1 continues counting and is unaffected by a compare match. ? bit 6 ? pwm1a: pulse width modulator a enable when set (one) this bit enables pwm mode based on comparator ocr1a in timer/counter1 and the counter value is reset to $00 in the cpu clock cycle after a compare match with ocr1c register value. ? bits 5:4 ? com1a[1:0]: comparator a output mode, bits 1 and 0 the com1a1 and com1a0 control bits determine any output pin action following a compare match with compare register a in timer/counter1. since the output pin action is an alternative function to an i/o port, the corresponding direction control bit must be set (one) in order to con- trol an output pin. in normal mode, the com1a1 and com1a0 control bits determine the output pin actions that affect pin pb1 (oc1a) as described in table 12-4 . note that oc1a is not connected in normal mode. in pwm mode, these bits have different functions. refer to table 12-1 on page 89 for a detailed description. ? bits 3:0 - cs1[3:0]: clock select bits 3, 2, 1, and 0 the clock select bits 3, 2, 1, and 0 define the prescaling source of timer/counter1. bit 7 6 5 4 3 2 1 0 0x30 ctc1 pwm1a com1a1 com1a0 cs13 cs12 cs11 cs10 tccr1 read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value 0 0 0 0 0 0 0 0 table 12-4. comparator a mode select in normal mode com1a1 com1a0 description 0 0 timer/counter comparator a di sconnected from output pin oc1a. 0 1 toggle the oc1a output line. 1 0 clear the oc1a output line. 1 1 set the oc1a output line table 12-5. timer/counter1 pr escale select cs13 cs12 cs11 cs10 asynchronous clocking mode synchronous clocking mode 0 0 0 0 t/c1 stopped t/c1 stopped 0001pck ck 0 0 1 0 pck/2 ck/2 0 0 1 1 pck/4 ck/4 93 2586n?avr?04/11 attiny25/45/85 the stop condition provides a timer enable/disable function. 12.3.2 gtccr ? general timer/counter1 control register ? bit 6 ? pwm1b: pulse width modulator b enable when set (one) this bit enables pwm mode based on comparator ocr1b in timer/counter1 and the counter value is reset to $00 in the cpu clock cycle after a compare match with ocr1c register value. ? bits 5:4 ? com1b[1:0]: comparator b output mode, bits 1 and 0 the com1b1 and com1b0 control bits determine any output pin action following a compare match with compare register b in timer/counter1. since the output pin action is an alternative function to an i/o port, the corresponding direction control bit must be set (one) in order to con- trol an output pin. in normal mode, the com1b1 and com1b0 control bits determine the output pin actions that affect pin pb4 (oc1b) as described in table 12-6 . note that oc1b is not connected in normal mode. 0 1 0 0 pck/8 ck/8 0 1 0 1 pck/16 ck/16 0 1 1 0 pck/32 ck/32 0 1 1 1 pck/64 ck/64 1 0 0 0 pck/128 ck/128 1 0 0 1 pck/256 ck/256 1 0 1 0 pck/512 ck/512 1 0 1 1 pck/1024 ck/1024 1 1 0 0 pck/2048 ck/2048 1 1 0 1 pck/4096 ck/4096 1 1 1 0 pck/8192 ck/8192 1 1 1 1 pck/16384 ck/16384 table 12-5. timer/counter1 prescale select (continued) cs13 cs12 cs11 cs10 asynchronous clocking mode synchronous clocking mode bit 7 6 5 4 3 2 1 0 0x2c tsm pwm1b com1b1 com1b0 foc1b foc1a psr1 psr0 gtccr read/write r/w r/w r/w r/w w w r/w r/w initial value 0 0 0 0 0 0 0 0 table 12-6. comparator b mode select in normal mode com1b1 com1b0 description 0 0 timer/counter comparator b di sconnected from output pin oc1b. 0 1 toggle the oc1b output line. 1 0 clear the oc1b output line. 1 1 set the oc1b output line 94 2586n?avr?04/11 attiny25/45/85 in pwm mode, these bits have different functions. refer to table 12-1 on page 89 for a detailed description. ? bit 3 ? foc1b: force output compare match 1b writing a logical one to this bit forces a change in the compare match output pin pb3 (oc1b) according to the values already set in com1 b1 and com1b0. if com1b1 and com1b0 written in the same cycle as foc1b, the new settings will be used. the force output compare bit can be used to change the output pin value regardless of the timer value. the automatic action pro- grammed in com1b1 and com1b0 takes place as if a compare match had occurred, but no interrupt is generated. the foc1b bit always reads as zero. foc1b is not in use if pwm1b bit is set. ? bit 2 ? foc1a: force output compare match 1a writing a logical one to this bit forces a change in the compare match output pin pb1 (oc1a) according to the values already set in com1 a1 and com1a0. if com1a1 and com1a0 written in the same cycle as foc1a, the new settings will be used. the force output compare bit can be used to change the output pin value regardless of the timer value. the automatic action pro- grammed in com1a1 and com1a0 takes place as if a compare match had occurred, but no interrupt is generated. the foc1a bit always reads as zero. foc1a is not in use if pwm1a bit is set. ? bit 1 ? psr1 : prescaler reset timer/counter1 when this bit is set (one), t he timer/counter prescaler (tcnt1 is unaffected) will be reset. the bit will be cleared by hard ware after the operation is performed. writing a zero to this bit will have no effect. this bit will always read as zero. 12.3.3 tcnt1 ? timer/counter1 this 8-bit register contains the value of timer/counter1. timer/counter1 is realized as an up counter with read and write access. due to synchronization of the cpu, timer/counter1 data written into timer/counter1 is de layed by one and half cpu clock cycles in synchronous mode and at most one cpu clock cycles for asynchronous mode. 12.3.4 ocr1a ?timer/counter1 output compare registera the output compare register a is an 8-bit read/write register. the timer/counter output compare register a contains data to be continuously compared with timer/counter1. actions on compare matches are specified in tccr1. a compare match does only occur if timer/counter1 counts to the ocr1a value. a software write that sets tcnt1 and ocr1a to the same value does not generate a compare match. a compare match will set the compar e interrupt flag ocf1a after a synchronization delay follow- ing the compare event. bit 76543210 0x2f msb lsb tcnt1 read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value 0 0 0 0 0 0 0 0 bit 76543210 0x2e msb lsb ocr1a read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value 0 0 0 0 0 0 0 0 95 2586n?avr?04/11 attiny25/45/85 12.3.5 ocr1b ? timer/counter1 output compare registerb the output compare register b is an 8-bit read/write register. the timer/counter output compare register b contains data to be continuously compared with timer/counter1. actions on compare matches are specified in tccr1. a compare match does only occur if timer/counter1 counts to the ocr1b value. a software write that sets tcnt1 and ocr1b to the same value does not generate a compare match. a compare match will set the compar e interrupt flag ocf1b after a synchronization delay follow- ing the compare event. 12.3.6 ocr1c ? timer/counter1 output compare registerc the output compare register c is an 8-bit read/write register. the timer/counter output compare register c co ntains data to be continuously compared with timer/counter1. a compare match does only oc cur if timer/counter1 counts to the ocr1c value. a software write that sets tcnt1 and ocr1c to the same value does not generate a compare match. if the ctc1 bit in tccr1 is set, a compare match will clear tcnt1. this register has the same function in normal mode and pwm mode. 12.3.7 timsk ? timer/counter interrupt mask register ? bit 7 ? res: reserved bit this bit is a reserved bit in the atti ny25/45/85 and always reads as zero. ? bit 6 ? ocie1a: timer/counter1 output compare interrupt enable when the ocie1a bit is set (one) and the i-bit in the status register is set (one), the timer/counter1 compare matcha, interrupt is enabled. the corresponding interrupt at vector $003 is executed if a compare matcha occurs. the compare flag in timer/counter1 is set (one) in the timer/counter interrupt flag register. ? bit 5 ? ocie1b: timer/counter1 output compare interrupt enable when the ocie1b bit is set (one) and the i-bit in the status register is set (one), the timer/counter1 compare matchb, interrupt is enabled. the corresponding interrupt at vector $009 is executed if a compare matchb occurs. the compare flag in timer/counter1 is set (one) in the timer/counter interrupt flag register. bit 76543210 0x2b msb lsb ocr1b read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value 0 0 0 0 0 0 0 0 bit 76543210 0x2d msb lsb ocr1c read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value 1 1 1 1 1 1 1 1 bit 7 6 5 4 3 2 1 0 0x39 ? ocie1a ocie1b ocie0a ocie0b toie1 toie0 ? timsk read/write r r/w r/w r/w r/w r/w r/w r initial value 0 0 0 0 0 0 0 0 96 2586n?avr?04/11 attiny25/45/85 ? bit 2 ? toie1: timer/counter1 overflow interrupt enable when the toie1 bit is set (one) and the i-bit in the status register is set (one), the timer/counter1 overflow interrupt is enabled. the corresponding interrupt (at vector $004) is executed if an overflow in timer/counter1 occurs . the overflow flag (timer1) is set (one) in the timer/counter interrupt flag register - tifr. ? bit 0 ? res: reserved bit this bit is a reserved bit in the atti ny25/45/85 and always reads as zero. 12.3.8 tifr ? timer/counter interrupt flag register ? bit 7 ? res: reserved bit this bit is a reserved bit in the atti ny25/45/85 and always reads as zero. ? bit 6 ? ocf1a: output compare flag 1a the ocf1a bit is set (one) when compare match occurs between timer/counter1 and the data value in ocr1a - output compare register 1a. ocf1a is cleared by hardware when executing the corresponding interrupt handling vector. alternatively, ocf1a is cleared, after synchroniza- tion clock cycle, by writing a logic one to the flag. when the i-bit in sreg, ocie1a, and ocf1a are set (one), the timer/counter1 a compare match interrupt is executed. ? bit 5 ? ocf1b: output compare flag 1b the ocf1b bit is set (one) when compare match occurs between timer/counter1 and the data value in ocr1b - output compare register 1a. ocf1b is cleared by hardware when executing the corresponding interrupt handling vector. alternatively, ocf1b is cleared, after synchroniza- tion clock cycle, by writing a logic one to the flag. when the i-bit in sreg, ocie1b, and ocf1b are set (one), the timer/counter1 b compare match interrupt is executed. ? bit 2 ? tov1: timer/counter1 overflow flag in normal mode (pwm1a=0 and pwm1b=0) the bit tov1 is set (one) when an overflow occurs in timer/counter1. the bit tov1 is clear ed by hardware when executing the corresponding interrupt handling vector. alternatively, tov1 is cleared, after synchronization clock cycle, by writing a logical one to the flag. in pwm mode (either pwm1a=1 or pwm1b=1) the bit tov1 is set (one) when compare match occurs between timer/counter1 and data valu e in ocr1c - output compare register 1c. when the sreg i-bit, and toie1 (timer/counter1 overflow interrupt enable), and tov1 are set (one), the timer/counter1 overflow interrupt is executed. ? bit 0 ? res: reserved bit this bit is a reserved bit in the atti ny25/45/85 and always reads as zero. bit 7 6 5 4 3 2 1 0 0x38 ?ocf1aocf1b ocf0a ocf0b tov1 tov0 ? tifr read/write r r/w r/w r/w r/w r/w r/w r initial value 0 0 0 0 0 0 0 0 97 2586n?avr?04/11 attiny25/45/85 12.3.9 pllcsr ? pll control and status register ? bit 7 ? lsm: low speed mode the high speed mode is enabled as default and t he fast peripheral clock is 64 mhz, but the low speed mode can be set by writing the lsm bit to one. then the fast peripheral clock is scaled down to 32 mhz. the low speed mode must be set, if the supply voltage is below 2.7 volts, because the timer/counter1 is not running fast enough on low voltage levels. it is highly recom- mended that timer/counter1 is stoppe d whenever the lsm bit is changed. note, that lsm can not be set if pll clk is used as system clock. ? bit 6:3 ? res : reserved bits these bits are reserved bits in the attiny25/45/85 and always read as zero. ? bit 2 ? pcke: pck enable the pcke bit change the timer/counter1 clock source. when it is set, the asynchronous clock mode is enabled and fast 64 mhz (or 32 mhz in low speed mode) pck clock is used as timer/counter1 clock source. if this bit is cl eared, the synchronous clock mode is enabled, and system clock ck is used as timer/counter1 clock source. this bit can be set only if plle bit is set. it is safe to set this bit only when the p ll is locked i.e the plock bit is 1. the bit pcke can only be set, if the pll has been enabled earlier. ? bit 1 ? plle: pll enable when the plle is set, the pll is started and if needed internal rc-oscilla tor is started as a pll reference clock. if pll is sele cted as a system clock source th e value for this bit is always 1. ? bit 0 ? plock: pll lock detector when the plock bit is set, the pll is locked to the reference clock. the plock bit should be ignored during initial pll lock-in sequence when pll frequency overshoots and undershoots, before reaching steady state. the steady state is obtained within 100 s. after pll lock-in it is recommended to check the plock bit before enabling pck for timer/counter1. bit 76543210 0x27 lsm - - - - pcke plle plock pllcsr read/write r/w r r r r r/w r/w r initial value 0 0 0 0 0 0 0/1 0 98 2586n?avr?04/11 attiny25/45/85 13. 8-bit timer/counter1 in attiny15 mode the attiny15 compatibility mode is selected by wr iting the code ?0011? to the cksel fuses (if any other code is written, the timer/counter1 is working in normal mode). when selected the attiny15 compatibility mode pr ovides an attiny15 backwa rd compatible prescaler and timer/counter. furthermore, the clocking system has same clock frequencies as in attiny15. 13.1 timer/counter1 prescaler figure 13-1 shows an attiny15 compatible prescaler. it has two prescaler units, a 10-bit pres- caler for the system clock (ck) and a 3-bit prescaler for the fast peripheral clock (pck). the clocking system of the timer/counter1 is alwa ys synchronous in the attiny15 compatibility mode, because the same rc oscillato r is used as a pll clock source (generates the input clock for the prescaler) and the avr core. figure 13-1. timer/counter1 prescaler the same clock selections as in attiny15 can be chosen for timer/counter1 from the output multiplexer, because the frequency of the fast peripheral clock is 25.6 mhz and the prescaler is similar in the attiny15 compatibility mode. the cl ock selections are pck, pck/2, pck/4, pck/8, ck, ck/2, ck/4, ck/8, ck/16, ck/32, ck/64, ck/128, ck/256, ck/512, ck/1024 and stop. 13.2 counter and compare units figure 13-2 shows timer/counter 1 synchronization re gister block diagram and synchronization delays in between registers. note that all cloc k gating details are not shown in the figure. the timer/counter1 register values go through the in ternal synchronization registers, which cause the input synchronization delay, before affecting the counter operation. the registers tccr1, gtccr, ocr1a and ocr1c can be read back right after writing the register. the read back values are delayed for the timer/counter1 (tcnt1) register and flags (ocf1a and tov1), because of the input and output synchronization. the timer/counter1 features a high resolution and a high accuracy usage with the lower pres- caling opportunities. it can also support an ac curate, high speed, 8-bit pulse width modulator (pwm) using clock speeds up to 25.6 mhz. in this mode, timer/counter1 and the output com- pare registers serve as a stand-alone pwm. refer to ?timer/counter1 in pwm mode? on page timer/counter1 count enable psr1 cs10 cs11 cs12 pck (25.6 mhz) 0 cs13 3-bit t/c prescaler pck/2 pck pck/4 pck/8 ck/2 ck/4 ck/8 ck/16 ck/32 ck/64 ck/128 ck/256 ck/512 ck/1024 10-bit t/c prescaler ck (1.6 mhz) ck clear clear 99 2586n?avr?04/11 attiny25/45/85 101 for a detailed description on this function. similarly, the high prescaling opportunities make this unit useful for lower spee d functions or exact timing fu nctions with infrequent actions. figure 13-2. timer/counter 1 synchronization register block diagram. timer/counter1 and the prescaler allow running the cpu from any clock source while the pres- caler is operating on the fast 25.6 mhz pck clock in the asynchronous mode. the following figure 13-3 shows the block diagram for timer/counter1. 8 -bit databu s ocr1a ocr1a_ s i tcnt_ s o ocr1c ocr1c_ s i tccr1 tccr1_ s i gtccr gtccr_ s i tcnt1 tcnt1_ s i ocf1a ocf1a_ s i tov1 tov1_ s i tov1_ s o ocf1a_ s o tcnt1 s a s a pcke ck pck io-regi s ter s inp u t s ynchroniz a tion regi s ter s timer/co u nter1 o u tp u t s ynchroniz a tion regi s ter s s ync mode a s ync mode 1 pck del a y no del a y ~1 ck del a y 1pck del a y no del a y tcnt1 ocf1a tov1 1..2 pck del a y ~1 ck del a y 1..2 pck del a y 100 2586n?avr?04/11 attiny25/45/85 figure 13-3. timer/counter1 block diagram two status flags (overflow and compare match) are found in the timer/counter interrupt flag register - tifr. control signals are found in the timer/counter control registers tccr1 and gtccr. the interrupt enable/disable settings ar e found in the timer/counter interrupt mask register - timsk. the timer/counter1 contains two output compare registers, ocr1a and ocr1c as the data source to be compared with the timer/counter1 contents. in normal mode the output compare functions are operational with ocr1a only. ocr1a determines action on the oc1a pin (pb1), and it can generate timer1 oc1a interrupt in normal mode and in pwm mode. ocr1c holds the timer/counter maximum value, i.e. the clear on compare match value. in the normal mode an overflow interrupt (tov1) is generated when timer/counter1 counts from $ff to $00, while in the pwm mode the overflow interrupt is generated when the timer/counter1 counts either from $ff to $00 or from ocr1c to $00. in pwm mode, ocr1a provides the data values against which the timer counter value is com- pared. upon compare match the pwm outputs (oc1a) is generated. in pwm mode, the timer counter counts up to the value specified in the output compare register ocr1c and starts again from $00. this feature a llows limiting the counter ?full? value to a specified value, lower than $ff. together with the many prescaler options, fl exible pwm frequency selection is provided. table 12-3 on page 91 lists clock selection and ocr1c va lues to obtain pwm frequencies from 20 khz to 250 khz in 10 khz steps and from 250 khz to 500 khz in 50 khz steps. higher pwm frequencies can be obtained at the expense of resolution. 8-bit databus timer int. flag register (tifr) timer/counter1 8-bit comparator t/c1 output compare register timer int. mask register (timsk) timer/counter1 (tcnt1) t/c clear t/c1 control logic tov1 tov1 toie0 toie1 ocie1a ocf1a ocf1a ck pck t/c1 over- flow irq oc1a (pb1) t/c1 compare match a irq global t/c control register 2 (gtccr) pwm1a foc1a (ocr1a) (ocr1c) 8-bit comparator t/c1 output compare register tov0 com1a1 com1a0 t/c control register 1 (tccr1) cs12 psr1 cs11 cs10 cs13 ctc1 101 2586n?avr?04/11 attiny25/45/85 13.2.1 timer/counter1 in pwm mode when the pwm mode is selected, timer/counter1 and the output compare register a - ocr1a form an 8-bit, free-running and glitch-free pwm generator with output on the pb1(oc1a). when the counter value match the content of ocr1a, the oc1a and output is set or cleared according to the com1a1/com1a0 bits in the timer/counter1 control register a - tccr1, as shown in table 13-1 . timer/counter1 acts as an up-counter, counting from $00 up to the value specified in the output compare register ocr1c, and starting from $00 up again. a compare match with ocr1c will set an overflow interrupt flag (tov1) after a synchronization delay following the compare event. note that in pwm mode, writing to the output compare register ocr1a, the data value is first transferred to a temporary location. the value is latched into ocr1a when the timer/counter reaches ocr1c. this prevents the occurrence of odd-length pwm pulses (glitches) in the event of an unsynchronized ocr1a. see figure 13-4 for an e xample. figure 13-4. effects of unsynchronized ocr latching during the time between the writ e and the latch operat ion, a read from oc r1a will read the con- tents of the temporary location. this means that the most recently writte n value always will read out of ocr1a. table 13-1. compare mode select in pwm mode com1a1 com1a0 effect on output compare pin 0 0 oc1a not connected. 0 1 oc1a not connected. 1 0 oc1a cleared on compare match. set when tcnt1 = $00. 1 1 oc1a set on compare match. cleared when tcnt1 = $00. pwm output oc1a pwm output oc1a unsynchronized oc1a latch synchronized oc1a latch counter value compare value counter value compare value compare value changes glitch compare value changes 102 2586n?avr?04/11 attiny25/45/85 when ocr1a contains $00 or the top value, as specified in ocr1c register, the output pb1(oc1a) is held low or high ac cording to the settings of com1a1/com1a0. this is shown in table 13-2 . in pwm mode, the timer overflow flag - tov1 is set when the tcnt1 counts to the ocr1c value and the tcnt1 is reset to $00. the timer overflow interrupt1 is executed when tov1 is set provided that timer overflow interrupt and glob al interrupts are enabled. this also applies to the timer output compare flags and interrupts. the pwm frequency can be derived from the timer/ counter clock frequency using the following equation: the duty cycle of the pwm waveform can be calculated using the following equation: ...where t pck is the period of the fast peripheral clock (1/25.6 mhz = 39.1 ns). resolution indicates how many bits are required to express the value in the ocr1c register. it can be calculated using the following equation: table 13-2. pwm outputs ocr1a = $00 or ocr1c com1a1 com1a0 ocr1a output oc1a 01$00l 0 1 ocr1c h 10$00l 1 0 ocr1c h 11$00h 1 1 ocr1c l table 13-3. timer/counter1 clock prescale se lect in the asynchronous mode pwm frequency clock select ion cs1[3:0] ocr1c resolution 20 khz pck/16 0101 199 7.6 30 khz pck/16 0101 132 7.1 40 khz pck/8 0100 199 7.6 50 khz pck/8 0100 159 7.3 60 khz pck/8 0100 132 7.1 70 khz pck/4 0011 228 7.8 f f tck1 ocr1c + 1 () ----------------------------------- - = d ocr1a 1 + () t tck1 t pck ? ocr1c 1 + () t tck1 ---------------------------------------------------------------------------- = r 2ocr1c 1 + () log = 103 2586n?avr?04/11 attiny25/45/85 13.3 register description 13.3.1 tccr1 ? timer/counter1 control register ? bit 7 ? ctc1 : clear timer/counter on compare match when the ctc1 control bit is set (one), timer/counter1 is reset to $00 in the cpu clock cycle after a compare match with ocr1a register. if the control bit is cleared, timer/counter1 contin- ues counting and is unaffected by a compare match. ? bit 6 ? pwm1a: pulse width modulator a enable when set (one) this bit enables pwm mode based on comparator ocr1a in timer/counter1 and the counter value is reset to $00 in the cpu clock cycle after a compare match with ocr1c register value. 80 khz pck/4 0011 199 7.6 90 khz pck/4 0011 177 7.5 100 khz pck/4 0011 159 7.3 110 khz pck/4 0011 144 7.2 120 khz pck/4 0011 132 7.1 130 khz pck/2 0010 245 7.9 140 khz pck/2 0010 228 7.8 150 khz pck/2 0010 212 7.7 160 khz pck/2 0010 199 7.6 170 khz pck/2 0010 187 7.6 180 khz pck/2 0010 177 7.5 190 khz pck/2 0010 167 7.4 200 khz pck/2 0010 159 7.3 250 khz pck 0001 255 8.0 300 khz pck 0001 212 7.7 350 khz pck 0001 182 7.5 400 khz pck 0001 159 7.3 450 khz pck 0001 141 7.1 500 khz pck 0001 127 7.0 table 13-3. timer/counter1 clock prescale select in the asynchronous mode (continued) pwm frequency clock select ion cs1[3:0] ocr1c resolution bit 7 6 5 4 3 2 1 0 0x30 ctc1 pwm1a com1a1 com1a0 cs13 cs12 cs11 cs10 tccr1a read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value 0 0 0 0 0 0 0 0 104 2586n?avr?04/11 attiny25/45/85 ? bits 5:4 ? com1a[1:0]: comparator a output mode, bits 1 and 0 the com1a1 and com1a0 control bits determine any output pin action following a compare match with compare register a in timer/counter1. output pin actions affect pin pb1 (oc1a). since this is an alternative function to an i/o po rt, the corresponding direction control bit must be set (one) in order to control an output pin. in pwm mode, these bits have different functions. refer to table 13-1 on page 101 for a detailed description. ? bits 3:0 ? cs1[3:0]: clock select bits 3, 2, 1, and 0 the clock select bits 3, 2, 1, and 0 define the prescaling source of timer/counter1. the stop condition provides a timer enable/disable function. table 13-4. comparator a mode select com1a1 com1a0 description 0 0 timer/counter comparator a di sconnected from output pin oc1a. 0 1 toggle the oc1a output line. 1 0 clear the oc1a output line. 1 1 set the oc1a output line table 13-5. timer/counter1 pr escale select cs13 cs12 cs11 cs10 t/c1 clock 0 0 0 0 t/c1 stopped 0001pck 0 0 1 0 pck/2 0 0 1 1 pck/4 0 1 0 0 pck/8 0101ck 0110ck/2 0111ck/4 1000ck/8 1001ck/16 1010ck/32 1011ck/64 1100ck/128 1101ck/256 1110ck/512 1 1 1 1 ck/1024 105 2586n?avr?04/11 attiny25/45/85 13.3.2 gtccr ? general timer/counter1 control register ? bit 2 ? foc1a: force output compare match 1a writing a logical one to this bit forces a change in the compare match output pin pb1 (oc1a) according to the values already set in com1 a1 and com1a0. if com1a1 and com1a0 written in the same cycle as foc1a, the new settings will be used. the force output compare bit can be used to change the output pin value regardless of the timer value. the automatic action pro- grammed in com1a1 and com1a0 takes place as if a compare match had occurred, but no interrupt is generated. the foc1a bit always reads as zero. foc1a is not in use if pwm1a bit is set. ? bit 1 ? psr1 : prescaler reset timer/counter1 when this bit is set (one), t he timer/counter prescaler (tcnt1 is unaffected) will be reset. the bit will be cleared by hard ware after the operation is performed. writing a zero to this bit will have no effect. this bit will always read as zero. 13.3.3 tcnt1 ? timer/counter1 this 8-bit register contains the value of timer/counter1. timer/counter1 is realized as an up counter with read and write access. due to synchronization of the cpu, timer/counter1 data written into timer/counter1 is delayed by one cpu clock cycle in synchronous mode and at most two cpu clock cycles for asynchronous mode. 13.3.4 ocr1a ? timer/counter1 output compare registera the output compare register a is an 8-bit read/write register. the timer/counter output compare register a contains data to be continuously compared with timer/counter1. actions on compare matches are specified in tccr1. a compare match does only occur if timer/counter1 counts to the ocr1a value. a software write that sets tcnt1 and ocr1a to the same value does not generate a compare match. a compare match will set the compar e interrupt flag ocf1a after a synchronization delay follow- ing the compare event. bit 7 6 5 4 3 2 1 0 0x2c tsm pwm1b com1b1 com1b0 foc1b foc1a psr1 psr0 gtccr read/write r/w r/w r/w r/w w w r/w r/w initial value 0 0 0 0 0 0 0 0 bit 76543210 0x2f msb lsb tcnt1 read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value 0 0 0 0 0 0 0 0 bit 76543210 0x2e msb lsb ocr1a read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value 0 0 0 0 0 0 0 0 106 2586n?avr?04/11 attiny25/45/85 13.3.5 ocr1c ? timer/counter1 output compare register c the output compare register b - ocr1b from attiny15 is replaced with the output compare register c - ocr1c that is an 8-bit read/write regi ster. this register has the same function as the output compare register b in attiny15. the timer/counter output compare register c co ntains data to be continuously compared with timer/counter1. a compare match does only oc cur if timer/counter1 counts to the ocr1c value. a software write that sets tcnt1 and ocr1c to the same value does not generate a compare match. if the ctc1 bit in tccr1 is set, a compare match will clear tcnt1. 13.3.6 timsk ? timer/counter interrupt mask register ? bit 7 ? res: reserved bit this bit is a reserved bit in the atti ny25/45/85 and always reads as zero. ? bit 6 ? ocie1a: timer/counter1 output compare interrupt enable when the ocie1a bit is set (one) and the i-bit in the status register is set (one), the timer/counter1 compare matcha, interrupt is enabled. the corresponding interrupt at vector $003 is executed if a compare matcha occurs. the compare flag in timer/counter1 is set (one) in the timer/counter interrupt flag register. ? bit 2 ? toie1: timer/counter1 overflow interrupt enable when the toie1 bit is set (one) and the i-bit in the status register is set (one), the timer/counter1 overflow interrupt is enabled. the corresponding interrupt (at vector $004) is executed if an overflow in timer/counter1 occurs . the overflow flag (timer1) is set (one) in the timer/counter interrupt flag register - tifr. ? bit 0 ? res: reserved bit this bit is a reserved bit in the atti ny25/45/85 and always reads as zero. 13.3.7 tifr ? timer/counter interrupt flag register ? bit 7 ? res: reserved bit this bit is a reserved bit in the atti ny25/45/85 and always reads as zero. bit 76543210 0x2d msb lsb ocr1c read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value 1 1 1 1 1 1 1 1 bit 7 6 5 4 3 2 1 0 0x39 ?ocie1a ocie1b ocie0a ocie0b toie1 toie0 ? timsk read/write r r/w r/w r/w r/w r/w r/w r initial value 0 0 0 0 0 0 0 0 bit 7 6 5 4 3 2 1 0 0x38 ?ocf1a ocf1b ocf0a ocf0b tov1 tov0 ? tifr read/write r r/w r/w r/w r/w r/w r/w r initial value 0 0 0 0 0 0 0 0 107 2586n?avr?04/11 attiny25/45/85 ? bit 6 ? ocf1a: output compare flag 1a the ocf1a bit is set (one) when compare match occurs between timer/counter1 and the data value in ocr1a - output compare register 1a. ocf1a is cleared by hardware when executing the corresponding interrupt handling vector. alternatively, ocf1a is cleared, after synchroniza- tion clock cycle, by writing a logic one to the flag. when the i-bit in sreg, ocie1a, and ocf1a are set (one), the timer/counter1 a compare match interrupt is executed. ? bit 2 ? tov1: timer/counter1 overflow flag the bit tov1 is set (one) when an overflow occu rs in timer/counter1. tov1 is cleared by hard- ware when executing the corresponding interrupt handling vector. alternatively, tov1 is cleared, after synchronization clock cycle, by writing a logical one to the flag. when the sreg i- bit, and toie1 (timer/counter1 overflow interrupt enable), and tov1 are set (one), the timer/counter1 overflow interrupt is executed. ? bit 0 ? res: reserved bit this bit is a reserved bit in the atti ny25/45/85 and always reads as zero. 13.3.8 pllcsr ? pll control and status register ? bits 6:3 ? res : reserved bits these bits are reserved bits in the attiny25/45/85 and always read as zero. ? bit 2 ? pcke: pck enable the bit pcke is always set in the attiny15 compatibility mode. ? bit 1 ? plle: pll enable the pll is always enabled in the attiny15 compatibility mode. ? bit 0 ? plock: pll lock detector when the plock bit is set, the pll is locked to the reference clock. the plock bit should be ignored during initial pll lock-in sequence when pll frequency overshoots and undershoots, before reaching steady state. the steady state is obtained within 100 s. after pll lock-in it is recommended to check the plock bit before enabling pck for timer/counter1. bit 76543210 0x27 lsm ? ? ? ? pcke plle plock pllcsr read/write r/w r r r r r/w r/w r initial value 0 0 0 0 0 0 0/1 0 108 2586n?avr?04/11 attiny25/45/85 14. dead time generator the dead time generator is provided for the timer/counter1 pwm output pairs to allow driving external power control switches safely. the dead time generator is a separate block that can be connected to timer/counter1 and it is used to insert dead times (non-overlapping times) for the timer/counter1 complementary output pairs (oc1a-oc1a and oc1b-oc1b ). the sharing of tasks is as follows: the timer/counter gener ates the pwm output and the dead time genera- tor generates the non-overlapping pwm output pair from the timer/counter pwm signal. two dead time generators are provided, one for eac h pwm output. the non-overlap time is adjust- able and the pwm output and it?s complementary output are adjusted separately, and independently for both pwm outputs. figure 14-1. timer/counter1 & dead time generators the dead time generation is based on the 4-bit down counters that count the dead time, as shown in figure 46. there is a dedicated prescaler in front of the dead time generator that can divide the timer/counter1 clock (pck or ck) by 1, 2, 4 or 8. this provides for large range of dead times that can be generated. the prescaler is controlled by two control bits dtps1[1:0] from the i/o register at addre ss 0x23. the block has also a ri sing and falling edge detector that is used to start the dead time counting period. depending on the edge, one of the transitions on the rising edges, oc1x or oc1x is delayed until the counter has counted to zero. the compara- tor is used to compare the counter with zero and stop the dead time insertion when zero has been reached. the counter is loaded with a 4-bi t dt1xh or dt1xl value from dt1x i/o register, depending on the edge of the pwm generator output when the dead time insertion is started. figure 14-2. dead time generator timer/counter1 oc1a oc1a oc1b oc1b dead time generator pwm generator pcke t15m pck ck dt1ah dt1bh dead time generator pwm1b pwm1a dt1al dt1bl clock control oc1x oc1x t/c1 clock pwm1x 4-bit counter comparator dt1xl dt1xh dt1x i/o register dead time prescaler dtps1[1:0] 109 2586n?avr?04/11 attiny25/45/85 the length of the counting period is user adjustable by selecting the dead time prescaler setting in 0x23 register, and selecting then the dead time value in i/o register dt1x. the dt1x register consists of two 4-bit fields, dt1xh and dt1xl that control the dead time periods of the pwm output and its? complementary output separately. thus the rising edge of oc1x and oc1x can have different dead time periods. the dead time is adjusted as the number of prescaled dead time generator clock cycles. figure 14-3. the complementary output pair 14.1 register description 14.1.1 dtps1 ? timer/counter1 dead time prescaler register 1 the dead time prescaler register, dtps1 is a 2-bit read/write register. ? bits 1:0 ? dtps1[1:0]: dead time prescaler the dedicated dead time prescaler in front of the dead time generator can divide the timer/counter1 clock (pck or ck) by 1, 2, 4 or 8 providing a large range of dead times that can be generated. the dead time prescaler is controlled by two bits dtps1[1:0] from the dead time prescaler register. these bits define the di vision factor of the dead time prescaler. the division factors are given in table 46. oc1x x = a or b t non-overlap / rising edge t non-overlap / falling edge oc1x pwm1x bit 76543210 0x23 dtps11 dtps10 dtps1 read/write rrrrrrr/wr/w initial value 0 0 0 0 0 0 0 0 table 14-1. division factors of the dead time prescaler dtps11 dtps10 prescaler di vides the t/c1 clock by 0 0 1x (no division) 012x 104x 118x 110 2586n?avr?04/11 attiny25/45/85 14.1.2 dt1a ? timer/counter1 dead time a the dead time value register a is an 8-bit read/write register. the dead time delay of is adjusted by the dead time value register, dt1a. the register consists of two fields, dt1ah[3:0] and dt1al[3:0], one for each complementary output. therefore a dif- ferent dead time delay can be adjusted for the rising edge of oc1a and the rising edge of oc1a . ? bits 7:4 ? dt1ah[3:0]: dead time value for oc1a output the dead time value for the oc1a output. the dead ti me delay is set as a number of the pres- caled timer/counter clocks. the minimum dead time is zero and the maximum dead time is the prescaled time/counter clock period multiplied by 15. ? bits 3:0 ? dt1al[3:0]: dead time value for oc1a output the dead time value for the oc1a output. the dead time delay is set as a number of the pres- caled timer/counter clocks. the minimum dead time is zero and the maximum dead time is the prescaled time/counter clock period multiplied by 15. 14.1.3 dt1b ? timer/counter1 dead time b the dead time value register bis an 8-bit read/write register. the dead time delay of is adjusted by the dead time value register, dt1b. the register consists of two fields, dt1bh[3:0] and dt1bl[3:0], one for each complementary output. therefore a dif- ferent dead time delay can be adjusted for the rising edge of oc1a and the rising edge of oc1a . ? bits 7:4 ? dt1bh[3:0]: dead time value for oc1b output the dead time value for the oc1b output. the dead ti me delay is set as a number of the pres- caled timer/counter clocks. the minimum dead time is zero and the maximum dead time is the prescaled time/counter clock period multiplied by 15. ? bits 3:0 ? dt1bl[3:0]: dead time value for oc1b output the dead time value for the oc1b output. the dead time delay is set as a number of the pres- caled timer/counter clocks. the minimum dead time is zero and the maximum dead time is the prescaled time/counter clock period multiplied by 15. bit 76543210 0x25 dt1ah3 dt1ah2 dt1ah1 dt1ah0 dt1al3 dt1al2 dt1al1 dt1al0 dt1a read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value 0 0 0 0 0 0 0 0 bit 76543210 0x24 dt1bh3 dt1bh2 dt1bh1 dt1bh0 dt1bl3 dt1bl2 dt1bl1 dt1bl0 dt1b read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value 0 0 0 0 0 0 0 0 111 2586n?avr?04/11 attiny25/45/85 15. usi ? universal serial interface 15.1 features ? two-wire synchronous data tr ansfer (master or slave) ? three-wire synchronous data transfer (master or slave) ? data received interrupt ? wakeup from idle mode ? wake-up from all sleep modes in two-wire mode ? two-wire start condition detect or with interr upt capability 15.2 overview the universal serial interface (usi), provides the basic hardware resources needed for serial communication. combined with a minimum of cont rol software, the usi allows significantly higher transfer rates and uses less code space than solutions based on software only. interrupts are included to minimize the processor load. a simplified block diagram of the usi is shown in figure 15-1 for actual placement of i/o pins refer to ?pinout attiny25/45/85? on page 2 . device-specific i/o register and bit locations are listed in the ?register descriptions? on page 118 . figure 15-1. universal serial interface, block diagram the 8-bit usi data register (usidr) contains the incoming and outgoing data. it is directly accessible via the data bus but a copy of the c ontents is also placed in the usi buffer register (usibr) where it can be retrieved later. if reading the usi data register directly, the register must be read as quickly as possible to ensure that no data is lost. the most significant bit of the usi data register is connected to one of two output pins (depend- ing on the mode configuration, see ?usicr ? usi control register? on page 120 ). there is a transparent latch between the output of the usi data register and the output pin, which delays data bu s u s ipf u s itc u s iclk u s ic s 0 u s ic s 1 u s ioif u s ioie u s idc u s i s if u s iwm0 u s iwm1 u s i s ie bit7 two-wire clock control unit do (o u tp u t only) di/ s da (inp u t/open dr a in) u s ck/ s cl (inp u t/open dr a in) 4- b it co u nter u s idr u s i s r dq le u s icr clock hold tim0 comp bit0 [1] 3 0 1 2 3 0 1 2 0 1 2 u s ibr 112 2586n?avr?04/11 attiny25/45/85 the change of data output to the opposite clock edge of the data input sampling. the serial input is always sampled from the data input (di) pin independent of the configuration. the 4-bit counter can be both read and written via the data bus, and it can generate an overflow interrupt. both the usi data register and the counter are clocked simultaneously by the same clock source. this allows the counter to count the number of bits received or transmitted and generate an interrupt when the transfer is complete. note that when an external clock source is selected the counter counts both clock edges. this means the counter registers the number of clock edges and not the number of data bits. the clock can be selected from three different sources: the usck pin, timer/counter0 compare match or from software. the two-wire clock control unit can be configured to generate an interrupt when a start condition has been detected on the two-wire bus. it can also be set to generate wait states by holding the clock pin low after a start condition is detected, or after the counter overflows. 15.3 functional descriptions 15.3.1 three-wire mode the usi three-wire mode is compliant to the serial peripheral interface (spi) mode 0 and 1, but does not have the slave select (ss) pin functionality. however, this feature can be implemented in software, if required. pin names used in this mode are di, do, and usck. figure 15-2. three-wire mode operat ion, simplified diagram figure 15-2 shows two usi units operating in three-wire mode, one as master and one as slave. the two usi data registers are interconnected in such way that after eight usck clocks, the data in each register has been interchanged. the same clock also increments the usi?s 4-bit counter. the counter overflow (interrupt) flag, or usioif, can therefore be used to determine when a transfer is completed. the clock is generated by the master device software by toggling the usck pin via the portb register or by writing a one to bit usitc bit in usicr. slave master bit7 bit6 bit5 bit4 bit3 bit2 bit1 bit0 do di usck bit7 bit6 bit5 bit4 bit3 bit2 bit1 bit0 do di usck portxn 113 2586n?avr?04/11 attiny25/45/85 figure 15-3. three-wire mode, timing diagram the three-wire mode timing is shown in figure 15-3 at the top of the figure is a usck cycle ref- erence. one bit is shifted into the usi data register (usidr) for eac h of these cycles. the usck timing is shown for both external clock modes. in external clock mode 0 (usics0 = 0), di is sampled at positive edges, and do is changed (u si data register is shifted by one) at nega- tive edges. in external clock mode 1 (usics0 = 1) the opposite edges with respect to mode 0 are used. in other words, data is sampled at ne gative and changes the output at positive edges. the usi clock modes corresponds to the spi data mode 0 and 1. referring to the timing diagram ( figure 15-3 ), a bus transfer involves the following steps: 1. the slave and master devices set up their data outputs and, depending on the protocol used, enable their output drivers (mark a and b). the output is set up by writing the data to be transmitted to the usi data regi ster. the output is enabled by setting the corresponding bit in the data direction register of port b. note that there is not a pre- ferred order of points a and b in the figure, but both must be at least one half usck cycle before point c, where the data is sampled. this is in order to ensure that the data setup requirement is satisfied. the 4-bit counter is reset to zero. 2. the master software generates a clock puls e by toggling the usck line twice (c and d). the bit values on the data input (di) pins are sampled by the usi on the first edge (c), and the data output is changed on the opposite edge (d). the 4-bit counter will count both edges. 3. step 2. is repeated eight times for a complete register (byte) transfer. 4. after eight clock pulses (i.e ., 16 clock edges) the counter w ill overflow and indicate that the transfer has been completed. if usi buffer registers are not used the data bytes that have been transferred must now be processed before a new transfer can be initi- ated. the overflow interrupt will wake up the processor if it is set to idle mode. depending of the protocol used the slave device can now set its output to high impedance. 15.3.2 spi master operation example the following code demonstrates how to use the usi as an spi master: spitransfer: out usidr,r16 ldi r16,(1< 117 2586n?avr?04/11 attiny25/45/85 enables its output. if the bit is set, a master read operation is in progress (i.e., the slave drives the sda line) the slave can hold the scl line low after the acknowledge (e). 6. multiple bytes can now be transmitted, all in same direction, until a stop condition is given by the master (f), or a new start condition is given. if the slave is not able to receive more data it does not acknowledge the data byte it has last received. when the master does a read operation it must terminate the operation by forcing the acknowledge bit low after the last byte transmitted. 15.3.5 start condition detector the start condition detector is shown in figure 15-6 . the sda line is delayed (in the range of 50 to 300 ns) to ensure valid sampling of the scl line. the start condition detector is only enabled in two-wire mode. figure 15-6. start condition detector, logic diagram the start condition detector is working asynchronously and can therefore wake up the processor from power-down sleep mode. however, the protocol used might have restrictions on the scl hold time. therefore, w hen using this feature the oscillator st art-up time (set by cksel fuses, see ?clock systems and their distribution? on page 23 ) must also be taken into consideration. refer to the description of the usisif bit on page 119 for further details. 15.3.6 clock speed considerations maximum frequency for scl and sck is f ck / 2. this is also the maximum data transmit and receive rate in both two- and three-wire mode . in two-wire slave mode the two-wire clock con- trol unit will hold the scl low unt il the slave is ready to receive more data. this may reduce the actual data rate in two-wire mode. 15.4 alternative usi usage the flexible design of the usi allows it to be used for other tasks when serial communication is not needed. below are some examples. 15.4.1 half-duplex asynchronous data transfer using the usi data register in three-wire mode it is possible to implement a more compact and higher performance uart than by software, only. 15.4.2 4-bit counter the 4-bit counter can be used as a stand-alone counter with overflow interrupt. note that if the counter is clocked externally, both cl ock edges will increment the counter value. sda scl write( usisif) clock hold usisif dq clr dq clr 118 2586n?avr?04/11 attiny25/45/85 15.4.3 12-bit timer/counter combining the 4-bit usi counter with one of the 8-bit timer/counters creates a 12-bit counter. 15.4.4 edge triggered external interrupt by setting the counter to maximum value (f) it can function as an additional external interrupt. the overflow flag and interrupt enable bit are th en used for the external interrupt. this feature is selected by the usics1 bit. 15.4.5 software interrupt the counter overflow interrupt can be used as a software interrupt triggered by a clock strobe. 15.5 register descriptions 15.5.1 usidr ? usi data register the usi data register can be accessed directly but a copy of the data can also be found in the usi buffer register. depending on the usics[1:0] bits of the usi control register a (left) shift operation may be per- formed. the shift operation can be synchronised to an external clock edge, to a timer/counter0 compare match, or directly to software via the usiclk bit. if a serial clock occurs at the same cycle the register is written, the register will c ontain the value written a nd no shift is performed. note that even when no wire mode is selected (usiwm[1:0] = 0) both the external data input (di/sda) and the external clock input (usck/scl) can still be used by the usi data register. the output pin (do or sda, depending on the wire mode) is connected via the output latch to the most significant bit (bit 7) of the usi data register. the output latch ensures that data input is sampled and data output is changed on opposite clock edges. the latch is open (transparent) during the first half of a serial clock cycle when an external clock source is selected (usics1 = 1) and constantly open when an internal clock s ource is used (usics1 = 0). the output will be changed immediately when a new msb is written as long as the latch is open. note that the data direction register bit corresponding to the output pin must be set to one in order to enable data output from the usi data register. 15.5.2 usibr ? usi buffer register instead of reading data from the usi data regi ster the usi buffer register can be used. this makes controlling the usi less time critical and gives the cpu more time to handle other pro- gram tasks. usi flags as set similarly as when reading the usidr register. the content of the usi data register is loaded to the usi buffer register when the transfer has been completed. bit 7 6 5 4 3 2 1 0 0x0f msb lsb usidr read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value 0 0 0 0 0 0 0 0 bit 7 6 5 4 3 2 1 0 0x10 msb lsb usibr read/write r r r r r r r r initial value 0 0 0 0 0 0 0 0 119 2586n?avr?04/11 attiny25/45/85 15.5.3 usisr ? usi status register the status register contains interrupt flags, line status flags and the counter value. ? bit 7 ? usisif: start condition interrupt flag when two-wire mode is selected, the usisif flag is set (to one) when a start condition has been detected. when three-wire mode or output disable mode has been selected any edge on the sck pin will set the flag. if usisie bit in usicr and the global interrupt enable flag are set, an interrupt will be gener- ated when this flag is set. the flag will only be cl eared by writing a logical one to the usisif bit. clearing this bit will release the start detec tion hold of uscl in two-wire mode. a start condition interr upt will wakeup the processor from all sleep modes. ? bit 6 ? usioif: counter overflow interrupt flag this flag is set (one) when the 4-bit counter overfl ows (i.e., at the transition from 15 to 0). if the usioie bit in usicr and the glob al interrupt enable flag are se t an interrupt will also be gener- ated when the flag is set. the flag will only be cleared if a one is wr itten to the usioif bit. clearing this bit will release the counter overfl ow hold of scl in two-wire mode. a counter overflow interrup t will wakeup the processor from idle sleep mode. ? bit 5 ? usipf: stop condition flag when two-wire mode is selected, the usipf flag is set (one) when a stop condition has been detected. the flag is cleared by writing a one to this bit. note that this is not an interrupt flag. this signal is useful when implementing two-wire bus master arbitration. ? bit 4 ? usidc: data output collision this bit is logical one when bit 7 in the usi data register differs from the physical pin value. the flag is only valid when two-wire mode is used. th is signal is useful when implementing two-wire bus master arbitration. ? bits 3:0 ? usicnt[3:0]: counter value these bits reflect the current 4-bit counter value. the 4-bit counter value can directly be read or written by the cpu. the 4-bit counter increments by one for each clock generated either by the external clock edge detector, by a timer/counter0 compare match, or by software using usiclk or usitc strobe bits. the clock source depends on the setting of the usics[1:0] bits. for external clock operation a special feature is added that allows the clock to be generated by writing to the usitc strobe bit. this feature is enabled by choosing an external clock source (usics1 = 1) and writing a one to the usiclk bit. note that even when no wire mode is selected (usiwm[1:0] = 0) the external clock input (usck/scl) can still be used by the counter. bit 7 6 5 4 3 2 1 0 0x0e usisif usioif usipf usidc usi cnt3 usicnt2 usicnt1 usicnt0 usisr read/write r/w r/w r/w r r/w r/w r/w r/w initial value 0 0 0 0 0 0 0 0 120 2586n?avr?04/11 attiny25/45/85 15.5.4 usicr ? usi control register the usi control register includes bits for interru pt enable, setting the wire mode, selecting the clock and clock strobe. ? bit 7 ? usisie: start condition interrupt enable setting this bit to one enables the start condition detector interrupt. if there is a pending interrupt and usisie and the global interrupt enable flag are set to one the interrupt will be executed immediately. refer to the usisif bit description on page 119 for further details. ? bit 6 ? usioie: counter overflow interrupt enable setting this bit to one enables the counter overflow interrupt. if there is a pending interrupt and usioie and the global interrup t enable flag are set to one th e interrupt will be executed imme- diately. refer to the usioif bit description on page 119 for further details. ? bits 5:4 ? usiwm[1:0]: wire mode these bits set the type of wire mode to be used, as shown in table 15-1 below. note: 1. the di and usck pins are renamed to serial data (sda) and serial clock (scl) respectively to avoid confusion between the modes of operation. bit 7 6 5 4 3 2 1 0 0x0d usisie usioie usiwm1 usiwm0 usics1 usics0 usiclk usitc usicr read/write r/w r/w r/w r/w r/w r/w w w initial value 0 0 0 0 0 0 0 0 table 15-1. relationship between usiw m[1:0] and usi operation usiwm1 usiwm0 description 00 outputs, clock hold, and start detector disabled. port pins operates as normal. 01 three-wire mode. uses do, di, and usck pins. the data output (do) pin overrides the corres ponding bit in the portb register. however, the corresponding ddrb bit still controls the data direction. when the port pin is set as input the pin pull-up is controlled by the portb bit. the data input (di) and serial clock (usck) pins do not affect the normal port operation. when operating as master, clock pulses are software generated by toggling the portb register, while the data direction is set to out put. the usitc bit in the usicr register can be used for this purpose. 10 two-wire mode. uses sda (di) and scl (usck) pins (1) . the serial data (sda) and the serial clock (scl) pins are bi-directional and use open- collector output drives. the output drivers are enabled by setting the corresponding bit for sda and scl in the ddrb register. when the output driver is enabled for the sda pin it will force the line sda low if the output of the usi data register or the corresp onding bit in the portb register is zero. otherwise, the sda line will not be driven (i.e ., it is released). when the scl pin output driver is enabled the scl line will be forced low if the corresponding bit in the portb register is zero, or by the start detector. otherwise the scl line will not be driven. the scl line is held low when a start detector detects a start condition and the output is enabled. clearing the start condition flag (usisif) releases the line. the sda and scl pin inputs is not affected by enabling this mode. pull-ups on the sda and scl port pin are disabled in two-wire mode. 11 two-wire mode. uses sda and scl pins. same operation as in two-wire mode above, except that the scl line is also held low when a counter overflow occurs, and until t he counter overflow flag (usioif) is cleared. 121 2586n?avr?04/11 attiny25/45/85 basically only the function of the outputs are affected by these bits. data and clock inputs are not affected by t he mode selected and will always have th e same function. the counter and usi data register can therefore be clocked externally and data input sampled, even when outputs are disabled. ? bits 3:2 ? usics[1:0]: clock source select these bits set the clock source for the usi data register and counter. the data output latch ensures that the output is changed at the opposite edge of the sampling of the data input (di/sda) when using external clock source (usck/scl). when software strobe or timer/counter0 compare match clock option is selected, the output latch is transparent and therefore the output is changed immediately. clearing the usics[1:0] bits enables software st robe option. when using this option, writing a one to the usiclk bit clocks both the usi data register and the counter. for external clock source (usics1 = 1), the usiclk bit is no longer used as a strobe, but selects between external clocking and software clocking by the usitc strobe bit. table 15-2 shows the relationship between the us ics[1:0] and usiclk setting and clock source used for the usi data register and the 4-bit counter. ? bit 1 ? usiclk: clock strobe writing a one to this bit location strobes the usi data register to shift one step and the counter to increment by one, provided that the software clock strobe option has been selected by writing usics[1:0] bits to zero. the output will change immediately when the clock strobe is executed, i.e., during the same instruction cycle. the value shifted into the usi data register is sampled the previous instruction cycle. when an external clock source is selected (usics1 = 1), the usiclk function is changed from a clock strobe to a clock select register. setting the usiclk bit in this case will select the usitc strobe bit as clock sour ce for the 4-bit counter (see table 15-2 ). the bit will be read as zero. ? bit 0 ? usitc: toggle clock port pin writing a one to this bit location toggles the usck/s cl value either from 0 to 1, or from 1 to 0. the toggling is independent of the setting in the data direction register, but if the port value is to be shown on the pin the corresponding ddr pin must be set as output (to one). this feature allows easy clock generation when implementing master devices. table 15-2. relationship between the usics[1:0] and usiclk setting usics1 usics0 usiclk clock sour ce 4-bit counter clock source 0 0 0 no clock no clock 0 0 1 software clock strobe (usiclk) software clock strobe (usiclk) 0 1 x timer/counter0 compare matc h timer/counter0 compare match 1 0 0 external, positive edge external, both edges 1 1 0 external, negative edge external, both edges 1 0 1 external, positive edge software clock strobe (usitc) 1 1 1 external, negative edge software clock strobe (usitc) 122 2586n?avr?04/11 attiny25/45/85 when an external clock source is selected (usics 1 = 1) and the usiclk bit is set to one, writ- ing to the usitc strobe bit will directly clock th e 4-bit counter. this allows an early detection of when the transfer is done when operating as a master device. the bit will read as zero. 123 2586n?avr?04/11 attiny25/45/85 16. analog comparator the analog comparator compares the input values on the positive pin ain0 and negative pin ain1. when the voltage on the positive pin ain0 is higher than the voltage on the negative pin ain1, the analog comparator output, aco, is set. the comparator can trigger a separate inter- rupt, exclusive to the analog comparator. the user can select interrupt triggering on comparator output rise, fall or toggle. a block diagram of t he comparator and its surrounding logic is shown in figure 16-1 . figure 16-1. analog comparator block diagram notes: 1. see table 16-1 below. see figure 1-1 on page 2 and table 10-5 on page 65 for analog comparator pin placement. 16.1 analog comparator multiplexed input when the analog to digital converter (adc) is configurated as single ended input channel, it is possible to select any of the adc[3:0] pins to replace the negative input to the analog compara- tor. the adc multiplexer is used to select this input, and consequently, the adc must be switched off to utilize this feature. if the analog comparator multiplexer enable bit (acme in adcsrb) is set and the adc is switched off (ade n in adcsra is zero), mux[1:0] in admux select the input pin to replace the negative input to the analog comparator, as shown in table 16-1 . if acme is cleared or aden is set, ain1 is applied to the negative input to the analog comparator. acd + _ vcc acbg aci aco acie acis1 acis0 i n terru pt select analog com pa rato r irq ain0 ain1 internal 1.1v referen ce adc multiplexer output acme aden (1) table 16-1. analog comparator multiplexed input acme aden mux[1:0] analog comparator negative input 0x xxain1 11 xxain1 10 00adc0 10 01adc1 10 10adc2 10 11adc3 124 2586n?avr?04/11 attiny25/45/85 16.2 register description 16.2.1 adcsrb ? adc control and status register b ? bit 6 ? acme: analog comparator multiplexer enable when this bit is written logic one and the adc is switched off (aden in adcsra is zero), the adc multiplexer selects the negative input to the analog comparator. when this bit is written logic zero, ain1 is applied to the negative input of the analog comparator. for a detailed description of this bit, see ?analog comparator multiplexed input? on page 123 . 16.2.2 acsr ? analog comparator control and status register ? bit 7 ? acd: analog comparator disable when this bit is written logic one , the power to the analog comparator is switched off. this bit can be set at any time to tu rn off the analog com parator. this will reduce power consumption in active and idle mode. when changing the acd bit, the analog comparator interrupt must be disabled by clearing the acie bit in acsr. otherwise an interrupt can occur when the bit is changed. ? bit 6 ? acbg: analog comparator bandgap select when this bit is set, a fixed bandgap reference vo ltage replaces the positive input to the analog comparator. when this bit is cleared, ain0 is ap plied to the positive input of the analog compar- ator. when the bandgap reference is used as input to the analog comparator, it will take a certain time for the voltage to stabilize. if not stabilized, the first conversion may give a wrong value. see ?internal voltage reference? on page 44 . ? bit 5 ? aco: analog comparator output the output of the analog comparator is synchronized and then directly connected to aco. the synchronization introduces a delay of 1 - 2 clock cycles. ? bit 4 ? aci: analog comparator interrupt flag this bit is set by hardware when a comparator output event triggers the interrupt mode defined by acis1 and acis0. the analog comparator interr upt routine is executed if the acie bit is set and the i-bit in sreg is set. aci is cleared by hardware when executing the corresponding inter- rupt handling vector. alternatively, aci is cleared by writing a logic one to the flag. ? bit 3 ? acie: analog comparator interrupt enable when the acie bit is written logic one and the i-bi t in the status register is set, the analog com- parator interrupt is activated. when written logic zero, the interrupt is disabled. ? bit 2 ? res: reserved bit this bit is a reserved bit in the attiny 25/45/85 and will alwa ys read as zero. bit 7 6543210 0x03 bin acme ipr ? ? adts2 adts1 adts0 adcsrb read/write r/w r/w r/w r r r/w r/w r/w initial value 0 0 0 0 0 0 0 0 bit 76543210 0x08 acd acbg aco aci acie ? acis1 acis0 acsr read/write r/w r/w r r/w r/w r r/w r/w initial value00n/a00000 125 2586n?avr?04/11 attiny25/45/85 ? bits 1:0 ? acis[1:0]: analog comparator interrupt mode select these bits determine which comparator events that trigger the analog comparator interrupt. the different settings are shown in table 16-2 . when changing the acis1/acis0 bits, the analog comparator interrupt must be disabled by clearing its interrupt enable bit in the acsr register. otherwise an interrupt can occur when the bits are changed. 16.2.3 didr0 ? digital in put disable register 0 ? bits 1:0 ? ain1d, ain0d: ai n[1:0] digital input disable when this bit is written logic one, the digital input buffer on the ain1/0 pin is disabled. the corre- sponding pin register bit will alwa ys read as zero when this bit is set. when an analog signal is applied to the ain1/0 pin and the digital input from this pin is not needed, this bit should be writ- ten logic one to reduce power consumption in the digital input buffer. table 16-2. acis1/acis0 settings acis1 acis0 interrupt mode 0 0 comparator interrupt on output toggle. 01reserved 1 0 comparator interrupt on falling output edge. 1 1 comparator interrupt on rising output edge. bit 76543210 0x14 ? ? adc0d adc2d adc3d adc1d ain1d ain0d didr0 read/write r r r/w r/w r/w r/w r/w r/w initial value00000000 126 2586n?avr?04/11 attiny25/45/85 17. analog to digital converter 17.1 features ? 10-bit resolution ? 1 lsb integral non-linearity ? 2 lsb absolute accuracy ? 65 - 260 s conversion time ? up to 15 ksps at maximum resolution ? four multiplexed single ended input channels ? two differential input channels with selectable gain ? temperature sensor input channel ? optional left adjustment for adc result readout ? 0 - v cc adc input voltage range ? selectable 1.1v / 2.56v adc voltage reference ? free running or single conversion mode ? adc start conversion by auto tr iggering on interrupt sources ? interrupt on adc conversion complete ? sleep mode no ise cancele ? unipolar / bibilar input mode ? input polarity reversal mode 17.2 overview the attiny25/45/85 features a 10-bit successive approximation analog to digital converter (adc). the adc is connected to a 4-channel anal og multiplexer which allows one differential voltage input and four single-ended voltage inputs cons tructed from the pins of port b. the dif- ferential input (pb3, pb4 or pb2, pb5) is equipped with a programmable gain stage, providing amplification step of 26 db (20x) on the differential input voltage before the a/d conversion. the single-ended voltage inputs refer to 0v (gnd). the adc contains a sample and hold circuit whic h ensures that the input voltage to the adc is held at a constant level during conversion. a block diagram of the adc is shown in figure 17-1 on page 127 . internal reference voltages of nominally 1.1v / 2.56v are provided on-chip. alternatively, v cc can be used as reference voltage for single ended channels. there is also an option to use an external voltage reference and turn-off the internal voltage reference. 127 2586n?avr?04/11 attiny25/45/85 figure 17-1. analog to digital converter block schematic 17.3 operation the adc converts an analog input voltage to a 10-bit digital value through successive approxi- mation. the minimum value represents gnd and the maximum value represents the voltage on v cc , the voltage on the aref pin or an internal 1.1v / 2.56v voltage reference. the voltage reference for the adc may be selected by writing to the refs[2:0] bits in admux. the vcc supply, the aref pin or an internal 1.1v / 2.56v voltage reference may be selected as the adc voltage reference. optionally the inte rnal 2.56v voltage reference may be decoupled by an external capacitor at the aref pin to improve noise immunity. the analog input channel and differential gain are se lected by writing to the mux[3:0] bits in admux. any of the four adc input pins adc[3:0] can be selected as single ended inputs to the adc. adc2 or adc0 can be selected as positi ve input and adc0, adc1 , adc2 or adc3 can be selected as negative input to the differential gain amplifier. if differential channels are selected, the differential gain stage amplifies the voltage difference between the selected input pair by the selected gain factor, 1x or 20x, according to the setting of the mux[3:0] bits in admux. this amplified valu e then becomes the analog input to the adc. if single ended channels are used, the gain amplifier is bypassed altogether. adc conversion complete irq 8-bit data bus 15 0 adc multiplexer select (admux) adc ctrl. & status a register (adcsra) adc data register (adch/adcl) adie adate adsc aden adif adif mux1 mux0 adps0 adps1 adps2 conversion logic 10-bit dac + - sample & hold comparator internal 1.1v/2.56v reference mux decoder mux2 aref adc3 adc2 adc1 adc0 refs[2:0] adlar channel selection adc[9:0] adc multiplexer output prescaler input mux trigger select adts[2:0] interrupt flags start + - gain selection gain amplifier neg. input mux single ended / differential selection temperature sensor adc4 adc ctrl. & status b register (adcsrb) bin ipr v cc 128 2586n?avr?04/11 attiny25/45/85 if adc0 or adc2 is selected as both the positive and negative input to the differential gain amplifier (adc0-adc0 or adc2-adc2), the remain ing offset in the gain stage and conversion circuitry can be measured directly as the result of the conversion. this figure can be subtracted from subsequent conversions with the same gain setting to reduce offset error to below 1 lsw. the on-chip temperature sensor is selected by writing the code ?1111? to the mux[3:0] bits in admux register when the adc4 ch annel is used as an adc input. the adc is enabled by setting the adc enable bit, aden in adcsra. voltage reference and input channel selections will not go into effect until aden is set. the adc does not consume power when aden is cleared, so it is recommended to switch off the adc before entering power saving sleep modes. the adc generates a 10-bit result which is pr esented in the adc data registers, adch and adcl. by default, the result is presented right adjusted, but can optionally be presented left adjusted by setting the adlar bit in admux. if the result is left adjusted and no more than 8-bit precision is required, it is sufficient to read adch. otherwise, adcl must be read first, then adch, to ensure that the content of the data registers belongs to the same conversion. once adcl is read, adc access to data registers is blocked. this means that if adcl has been r ead, and a conversion completes before adch is read, neither register is updated and the result fr om the conversion is lost. when adch is read, adc access to the adch and ad cl registers is re-enabled. the adc has its own interrupt which can be triggered when a conversion completes. when adc access to the data registers is prohibited between r eading of adch and ad cl, the in terrupt will trigger even if the result is lost. 17.4 starting a conversion a single conversion is started by writing a l ogical one to the adc start conversion bit, adsc. this bit stays high as long as the conversi on is in progress and will be cleared by hardware when the conversion is completed. if a different data channel is selected while a conversion is in progress, the adc will finish the current conv ersion before performing the channel change. alternatively, a conversion can be triggered automatically by various sources. auto triggering is enabled by setting the adc auto trigger enable bi t, adate in adcsra. the trigger source is selected by setting the adc trigger select bits, adts in adcsrb (see description of the adts bits for a list of the trigger sources). when a positive edge occurs on the selected trigger signal, the adc prescaler is reset and a conversion is st arted. this provides a method of starting con- versions at fixed intervals. if the trigger signal still is set when the conversion completes, a new conversion will not be star ted. if another positive edge occurs on the trigger si gnal during con- version, the edge will be ignored. note that an interrupt flag will be set even if the specific interrupt is disabled or the global interrupt enable bit in sreg is cleared. a conversion can thus be triggered without causing an interrupt. however, the interrupt flag must be cleared in order to trigger a new conversion at the next interrupt event. using the adc interrupt flag as a trigger source makes the adc start a new conversion as soon as the ongoing conversion has finished. the adc then operates in free running mode, con- stantly sampling and updating the adc data register. the first conversion must be started by writing a logical one to the adsc bit in adcs ra. in this mode the adc will perform successive conversions independently of whether the a dc interrupt flag, adif is cleared or not. 129 2586n?avr?04/11 attiny25/45/85 figure 17-2. adc auto trigger logic if auto triggering is enabled, single conversi ons can be started by writing adsc in adcsra to one. adsc can also be used to determine if a conversion is in progress. the adsc bit will be read as one during a conversion, independently of how the conversion was started. 17.5 prescaling and conversion timing figure 17-3. adc prescaler by default, the successive approximation circ uitry requires an input clock frequency between 50 khz and 200 khz to get maximum resolution. if a lower resolution than 10 bits is needed, the input clock frequency to the adc can be higher than 200 khz to get a higher sample rate. it is not recommended to use a higher input clock frequency than 1 mhz. the adc module contains a prescaler, which generates an acceptable adc clock frequency from any cpu frequency above 100 khz. the presca ling is set by the adps bits in adcsra. the prescaler starts counting from the moment the adc is switched on by setting the aden bit in adcsra. the prescaler keeps running for as lo ng as the aden bit is set, and is continuously reset when aden is low. adsc adif source 1 source n adts[2:0] conversion logic prescaler start clk adc . . . . edge detector adate 7-bit adc prescaler adc clock source ck adps0 adps1 adps2 ck/128 ck/2 ck/4 ck/8 ck/16 ck/32 ck/64 reset aden start 130 2586n?avr?04/11 attiny25/45/85 when initiating a single ended conversion by se tting the adsc bit in adcsra, the conversion starts at the following rising edge of the adc clock cycle. a normal conversion takes 13 adc clock cycles. the first conversion after the adc is switched on (aden in adcsra is set) takes 25 adc clock cycles in order to initialize the analog circuitry, as shown in figure 17-4 below. figure 17-4. adc timing diagram, first conver sion (single conversion mode) the actual sample-and-hold takes place 1.5 adc clock cycles after the start of a normal conver- sion and 13.5 adc clock cycles after the start of an first conv ersion. when a conversion is complete, the result is written to the adc data re gisters, and adif is set. in single conversion mode, adsc is cleared simultaneously. the software may then set adsc again, and a new conversion will be init iated on the first rising adc clock edge. figure 17-5. adc timing diagram, single conversion when auto triggering is used, the prescaler is reset when the trigger event occurs. this assures a fixed delay from the trigger event to the start of conversion. in this mode, the sample-and-hold takes place two adc clock cycles after the rising edge on the trigger source signal. three addi- tional cpu clock cycles are used for synchronization logic. sign and msb of result lsb of result adc clock adsc sample & hold adif adch adcl cycle number aden 1 212 13 14 15 16 17 18 19 20 21 22 23 24 25 1 2 first conversion next conversion 3 mux and refs update mux and refs update conversion complete 1 2 3 4 5 6 7 8 9 10 11 12 13 sign and msb of result lsb of result adc clock adsc adif adch adcl cycle number 12 one conversion next conversion 3 sample & hold mux and refs update conversion complete mux and refs update 131 2586n?avr?04/11 attiny25/45/85 figure 17-6. adc timing diagram, auto triggered conversion in free running mode, a new conversion will be started immediately after the conversion com- pletes, while adsc remains high. figure 17-7. adc timing diagram, free running conversion for a summary of conversion times, see table 17-1 . table 17-1. adc conversion time condition sample & hold (cycles from start of conversion) total conversion time (cycles) first conversion 13.5 25 normal conversions 1.5 13 auto triggered conversions 2 13.5 1 2 3 4 5 6 7 8 9 10 11 12 13 sign and msb of result lsb of result adc clock trigger source adif adch adcl cycle number 12 one conversion next conversion conversion complete prescaler reset adate prescaler reset sample & hold mux and refs update 11 12 13 sign and msb of result lsb of result adc clock adsc adif adch adcl cycle number 12 one conversion next conversion 34 conversion complete sample & hold mux and refs update 132 2586n?avr?04/11 attiny25/45/85 17.6 changing channel or reference selection the mux[3:0] and refs[2:0] bits in the admux register are single buffered through a tempo- rary register to which the cpu has random access. this ensures that the channels and voltage reference selection only takes place at a safe point during the conversion. the channel and volt- age reference selection is continuously updated until a conversion is started. once the conversion starts, the channel and voltage referenc e selection is locked to ensure a sufficient sampling time for the adc. continuous updating resumes in the last adc clock cycle before the conversion completes (adif in adcsra is set). note that the conversion starts on the following rising adc clock edge after adsc is written. th e user is thus advised not to write new channel or voltage reference selection values to admux until one adc clock cycle after adsc is written. if auto triggering is used, the exact time of t he triggering event can be indeterministic. special care must be taken when updating the admux register, in order to control which conversion will be affected by the new settings. if both adate and aden is written to one, an interrupt event can occur at any time. if the admux register is changed in this period, the user cannot tell if the next conversion is based on the old or the new settings. admux can be safely updated in the following ways: a. when adate or aden is cleared. b. during conversion, minimum one adc clock cycle after the trigger event. c. after a conversion, before the interrupt flag used as trigger source is cleared. when updating admux in one of these conditions, the new settings will affect the next adc conversion. 17.6.1 adc input channels when changing channel selections, the user should observe the following guidelines to ensure that the correct channel is selected: in single conversion mode, always select the channel before starting the conversion. the chan- nel selection may be changed one adc clock cycle after writing one to adsc. however, the simplest method is to wait for the conversion to complete before changing the channel selection. in free running mode, always select the channel before starting the first conversion. the chan- nel selection may be changed one adc clock cycle after writing one to adsc. however, the simplest method is to wait for the first conversion to complete, and then change the channel selection. since the next conver sion has already started automati cally, the next result will reflect the previous channel selection. subsequent conversions will refl ect the new channel selection. 17.6.2 adc voltage reference the voltage reference for the adc (v ref ) indicates the conversion range for the adc. single ended channels that exceed v ref will result in code s close to 0x3ff. v ref can be selected as either v cc , or internal 1.1v / 2.56v voltage reference, or external aref pin. the first adc con- version result after switching voltage reference source may be inaccurate, and the user is advised to discard this result. 17.7 adc noise canceler the adc features a noise canceler that enables conversion during sleep mode to reduce noise induced from the cpu core and other i/o peripherals. the noise canceler can be used with adc 133 2586n?avr?04/11 attiny25/45/85 noise reduction and idle mode. to make use of this feature, the following procedure should be used: ? make sure that the adc is enabled and is not busy converting. single conversion mode must be selected and the adc conversion complete interrupt must be enabled. ? enter adc noise reduction mode (or idle mode ). the adc will start a conversion once the cpu has been halted. ? if no other interrupts occur be fore the adc conversion comple tes, the adc interrupt will wake up the cpu and execute the adc conversion complete interrupt routine. if another interrupt wakes up the cpu before the adc conversion is complete, that interrupt will be executed, and an adc conversion complete interrup t request will be gene rated when the adc conversion completes. the cpu will remain in active mode until a new sleep command is executed. note that the adc will not be automatically turned off when entering other sleep modes than idle mode and adc noise reduction mode. the user is advised to write zero to aden before enter- ing such sleep modes to avoid excessive power consumption. 17.8 analog input circuitry the analog input circuitry for single ended channels is illustrated in figure 17-8. an analog source applied to adcn is subjected to the pin capacitance and input leakage of that pin, regard- less of whether that channel is selected as input for the adc. when the channel is selected, the source must drive the s/h capacitor through the series resistance (combined resistance in the input path). figure 17-8. analog input circuitry the adc is optimized for analog signals wit h an output impedance of approximately 10 k or less. if such a source is used, the sampling time will be negligible. if a source with higher imped- ance is used, the sampling time will depend on how long time the source nee ds to charge the s/h capacitor, with can vary widely. the user is recommended to only use low impedant sources with slowly varying signals, since this minimizes the required charge transfer to the s/h capacitor. signal components higher than the nyquist frequency (f adc /2) should not be present to avoid distortion from unpredictable signal convolution. the user is advised to remove high frequency components with a low-pass filter before applying the signals as inputs to the adc. adcn i ih 1..100 k c s/h = 14 pf v cc /2 i il 134 2586n?avr?04/11 attiny25/45/85 17.9 noise canceling techniques digital circuitry inside and outside the device ge nerates emi which might affect the accuracy of analog measurements. if conversion accuracy is critical, the noise level can be reduced by applying the following techniques: ? keep analog signal paths as short as possible. ? make sure analog tracks run over the analog ground plane. ? keep analog tracks well away from high-speed switching digital tracks. ? if any port pin is used as a digital output, it mustn?t switch while a conversion is in progress. ? place bypass capacitors as close to v cc and gnd pins as possible. where high adc accuracy is required it is recommended to use adc noise reduction mode, as described in section 17.7 on page 132 . this is especially the case when system clock frequency is above 1 mhz, or when the adc is used for reading the internal temperature sensor, as described in section 17.12 on page 137 . a good system design with properly placed, external bypass capacitors does reduce the need for using adc noise reduction mode 17.10 adc accuracy definitions an n-bit single-ended adc converts a voltage linearly between gnd and v ref in 2 n steps (lsbs). the lowest code is read as 0, and the highest code is read as 2 n -1. several parameters describe the deviation from the ideal behavior, as follows: ? offset: the deviation of the first transition (0x000 to 0x001) compared to the ideal transition (at 0.5 lsb). ideal value: 0 lsb. figure 17-9. offset error output code v ref input voltage ideal adc actual adc offset error 135 2586n?avr?04/11 attiny25/45/85 ? gain error: after adjusting for offset, the gain error is found as the deviation of the last transition (0x3fe to 0x3ff) compared to the ideal transition (at 1.5 lsb below maximum). ideal value: 0 lsb figure 17-10. gain error ? integral non-linearity (inl): after adjusting for offset and gain error, the inl is the maximum deviation of an actual transition compared to an ideal transition for any code. ideal value: 0 lsb. figure 17-11. integral non-linearity (inl) output code v ref input voltage ideal adc actual adc gain error output code v ref input voltage ideal adc actual adc inl 136 2586n?avr?04/11 attiny25/45/85 ? differential non-linearity (dnl): the maximum deviation of the actual code width (the interval between two adjacent transitions) from the ideal code width (1 lsb). ideal value: 0 lsb. figure 17-12. differential non-linearity (dnl) ? quantization error: due to the quantization of the input voltage into a finite number of codes, a range of input voltages (1 lsb wide) will code to the same value. always 0.5 lsb. ? absolute accuracy: the maximum deviation of an actual (unadjusted) transition compared to an ideal transition for any code. this is the compound effect of offset, gain error, differential error, non-linearity, and quantization error. ideal value: 0.5 lsb. 17.11 adc conversion result after the conversion is complete (adif is high ), the conversion result can be found in the adc result registers (adcl, adch) . the form of the conversion result depends on the type of the conversio as there are three types of conversions: single ended c onversion, unipolar differential conversion and bipolar differential conversion. 17.11.1 single ended conversion for single ended conversion, the result is where v in is the voltage on the selected input pin and v ref the selected voltage reference (see table 17-3 on page 138 and table 17-4 on page 139 ). 0x000 represents analog ground, and output code 0x3ff 0x000 0 v ref input voltage dnl 1 lsb adc v in 1024 ? v ref -------------------------- = 137 2586n?avr?04/11 attiny25/45/85 0x3ff represents the selected voltage reference minus one lsb. the result is presented in one- sided form, from 0x3ff to 0x000. 17.11.2 unipolar differential conversion if differential channels and an unipolar input mode are used, the result is where v pos is the voltage on the positive input pin, v neg the voltage on the negative input pin, and v ref the selected voltage reference (see table 17-3 on page 138 and table 17-4 on page 139 ). the voltage on the positive pin must always be larger than the voltage on the negative pin or otherwise the voltage difference is saturated to zero. the result is presented in one-sided form, from 0x000 (0d) to 0x3ff (+1023d). the gain is either 1x or 20x. 17.11.3 bipolar differential conversion as default the adc converter operates in the unipolar input mode, but the bipolar input mode can be selected by writting the bin bit in the adcsrb to one. in the bipolar input mode two- sided voltage differences are allowed and thus the voltage on the negative input pin can also be larger than the voltage on the positive input pin. if differential channels and a bipolar input mode are used, the result is where v pos is the voltage on the positive input pin, v neg the voltage on the negative input pin, and v ref the selected voltage reference. the result is presented in two?s complement form, from 0x200 (-512d) through 0x000 (+0d) to 0x1ff (+511d). the gain is either 1x or 20x. however, if the signal is not bipolar by nature (9 bits + sign as the 10th bit), this scheme loses one bit of the converter dynamic range. then, if the user wants to perform the conversion with the maximum dynamic range, the user can perfor m a quick polarity check of the result and use the unipolar differential conversi on with selectable differential i nput pairs (see the input polarity reversal mode ie. the ipr bit in the ?adcsrb ? adc control and status register b? on page 141 ). when the polarity check is performed, it is su fficient to read the m sb of the result (adc9 in adch). if the bit is one, the result is negative, and if this bit is zero, the result is positive. 17.12 temperature measurement the temperature measurement is based on an on-ch ip temperature sensor that is coupled to a single ended adc4 channel. selecting the adc4 channel by writing the mux[3:0] bits in admux register to ?1111? enables the temperature sensor. the internal 1.1v reference must also be selected for the adc reference source in the temperature sensor measurement. when the temperature sensor is enabled, the adc conver ter can be used in single conversion mode to measure the voltage over the temperature sensor. the measured voltage has a linear relationship to the temperature as described in table 17-2 the sensitivity is approximately 1 lsb / c and the accuracy depends on the method of user cal- ibration. typically, the measurement accuracy after a single temperature calibration is 10 c, adc v pos v neg ? () 1024 ? v ref ------------------------------------------------------- - gain ? = adc v pos v neg ? () 512 ? v ref ---------------------------------------------------- - gain ? = 138 2586n?avr?04/11 attiny25/45/85 assuming calibration at room temperature. better accuracies are achieved by using two temperature points for calibration. the values described in table 17-2 are typical values. however, due to process variation the temperature sensor output voltage varies from one chip to another. to be capable of achieving more accurate results the temperature measurement can be calibrated in the application soft- ware. the sofware calibration can be done using the formula: t = k * [(adch << 8) | adcl] + t os where adch and adcl are the adc data registers, k is the fixed slope coefficient and t os is the temperature sensor offset. typically, k is very close to 1.0 and in single-point calibration the coefficient may be omitted. where higher accura cy is required the slope coefficient should be evaluated based on measurements at two temperatures. 17.13 register description 17.13.1 admux ? adc multiplexer selection register ? bits 7:6, 4 ? refs[2:0]: voltage reference selection bits these bits select the voltage reference (v ref ) for the adc, as shown in table 17-3 . if these bits are changed duri ng a conversion, t he change will not go in effe ct until this conversion is complete (adif in adcsr is set). whenever these bits are changed, the next conversion will take 25 adc clock cycles. when differential channels and gain are used, using v cc or an external aref higher than (v cc - 1v) as a voltage reference is not recommended as this will affect the adc accuracy. note: 1. the device requries a supply voltage of 3v in order to generate 2.56v reference voltage. table 17-2. temperature vs. sensor output voltage (typical case) temperature -40 c+25 c+85 c adc 230 lsb 300 lsb 370 lsb bit 76543210 0x07 refs1 refs0 adlar refs2 mux3 mux2 mux1 mux0 admux read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value00000000 table 17-3. voltage reference selections for adc refs2 refs1 refs0 voltage reference (v ref ) selection x00v cc used as voltage reference, disconnected from pb0 (aref). x01 external voltage reference at pb0 (aref) pin, internal voltage reference turned off. 0 1 0 internal 1.1v voltage reference. 0 1 1 reserved 110 internal 2.56v voltage reference without external bypass capacitor, disconnected from pb0 (aref) (1) . 111 internal 2.56v voltage reference with external bypass capacitor at pb0 (aref) pin (1) . 139 2586n?avr?04/11 attiny25/45/85 ? bit 5 ? adlar: adc left adjust result the adlar bit affects the presentation of the adc conversion result in the adc data register. write one to adlar to left adjust the result. otherwise, the result is right adjusted. changing the adlar bit will affect t he adc data register immediately, regardless of any ongoing conver- sions. for a comple te description of this bit, see ?adcl and adch ? the adc data register? on page 141 . ? bits 3:0 ? mux[3:0]: analog channel and gain selection bits the value of these bits selects which combination of analog inputs are connected to the adc. in case of differential input (adc0 - adc1 or adc2 - adc3), gain selection is also made with these bits. selecting adc2 or adc0 as both inputs to the differential gain stage enables offset mea- surements. selecting the single-ended channel adc4 enables the temperature sensor. refer to table 17-4 for details. if these bits are changed during a conversi on, the change will not go into effect until this conversion is co mplete (adif in adcsra is set). note: 1. for offset calibration, only. see ?operation? on page 127. 2. after switching to internal voltage reference the adc requires a settling time of 1ms before measurements are stable. conversions starting before this may not be reliable. the adc must be enabled during the settling time. 3. for temperature sensor. table 17-4. input channel selections mux[3:0] single ended input positive differential input negative differential input gain 0000 adc0 (pb5) n/a 0001 adc1 (pb2) 0010 adc2 (pb4) 0011 adc3 (pb3) 0100 n/a adc2 (pb4) adc2 (pb4) 1x 0101 (1) adc2 (pb4) adc2 (pb4) 20x 0110 adc2 (pb4) adc3 (pb3) 1x 0111 adc2 (pb4) adc3 (pb3) 20x 1000 adc0 (pb5) adc0 (pb5) 1x 1001 adc0 (pb5) adc0 (pb5) 20x 1010 adc0 (pb5) adc1 (pb2) 1x 1011 adc0 (pb5) adc1 (pb2) 20x 1100 (2) v bg n/a 1101 gnd 1110 n/a 1111 (3) adc4 140 2586n?avr?04/11 attiny25/45/85 17.13.2 adcsra ? adc control and status register a ? bit 7 ? aden: adc enable writing this bit to one enables the adc. by writi ng it to zero, the adc is turned off. turning the adc off while a conversion is in prog ress, will terminate this conversion. ? bit 6 ? adsc: adc start conversion in single conversion mode, write this bit to one to start each conversion. in free running mode, write this bit to one to start the first conversion. the first conversion after adsc has been written after the adc has been enabled, or if adsc is written at the same time as the adc is enabled, will take 25 adc clock cycles instead of the norma l 13. this first conversi on performs initializa- tion of the adc. adsc will read as one as long as a conversion is in progress. when the co nversion is complete, it returns to zero. writing zero to this bit has no effect. ? bit 5 ? adate: adc auto trigger enable when this bit is written to on e, auto triggering of the adc is enabled. the adc will start a con- version on a positive edge of the selected trigger signal. the trigger source is selected by setting the adc trigger select bits, adts in adcsrb. ? bit 4 ? adif: adc interrupt flag this bit is set when an adc conversion completes and the data registers are updated. the adc conversion complete interrupt is executed if th e adie bit and the i-bit in sreg are set. adif is cleared by hardware when executing the corres ponding interrupt handling vector. alternatively, adif is cleared by writing a logical one to the flag. beware that if doing a read-modify-write on adcsra, a pending interrupt can be disabled. this also applies if the sbi and cbi instructions are used. ? bit 3 ? adie: adc interrupt enable when this bit is written to one and the i-bit in sreg is set, the adc conversion complete inter- rupt is activated. ? bits 2:0 ? adps[2:0]: adc prescaler select bits these bits determine the division factor betwee n the system clock frequency and the input clock to the adc. bit 76543210 0x06 aden adsc adate adif adie adps2 adps1 adps0 adcsra read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value00000000 table 17-5. adc prescaler selections adps2 adps1 adps0 division factor 000 2 001 2 010 4 011 8 100 16 141 2586n?avr?04/11 attiny25/45/85 17.13.3 adcl and adch ? the adc data register 17.13.3.1 adlar = 0 17.13.3.2 adlar = 1 when an adc conversion is complete, the result is found in these two registers. when adcl is read, the adc data register is not updated unt il adch is read. consequently, if the result is left adjusted and no more than 8-bit precision is required, it is sufficient to read adch. otherwise, adcl must be read first, then adch. the adlar bit in admux, and the muxn bits in admux affect the way the result is read from the registers. if adlar is set, the result is left adjusted. if adla r is cleared (default), the result is right adjusted. ? bits 9:0 - adc[9:0]: adc conversion result these bits represent the result from the conversion, as detailed in ?adc conversion result? on page 136 . 17.13.4 adcsrb ? adc control and status register b ? bit 7 ? bin: bipolar input mode the gain stage is working in the unipolar mode as default, but the bipolar mode can be selected by writing the bin bit in the adcsrb register. in the unipolar mode only one-sided conversions 101 32 110 64 1 1 1 128 table 17-5. adc prescaler selections (continued) adps2 adps1 adps0 division factor bit 151413121110 9 8 0x05 ?????? adc9 adc8 adch 0x04 adc7 adc6 adc5 adc4 adc3 adc2 adc1 adc0 adcl 76543210 read/write rrrrrrrr rrrrrrrr initial value00000000 00000000 bit 151413121110 9 8 0x05 adc9 adc8 adc7 adc6 adc5 adc4 adc3 adc2 adch 0x04 adc1 adc0 ?????? adcl 76543210 read/write rrrrrrrr rrrrrrrr initial value00000000 00000000 bit 7 6543210 0x03 bin acme ipr ? ? adts2 adts1 adts0 adcsrb read/write r/w r/w r/w r r r/w r/w r/w initial value 0 0 0 0 0 0 0 0 142 2586n?avr?04/11 attiny25/45/85 are supported and the voltage on the positive input must always be larger than the voltage on the negative input. otherwise the result is saturated to the voltage reference. in the bipolar mode two-sided conversions are supported and the result is represented in the two?s complement form. in the unipolar mode the resolution is 10 bits and the bipolar mode the resolution is 9 bits + 1 sign bit. ? bit 5 ? ipr: input polarity reversal the input polarity mode allows software selectable differential input pairs and full 10 bit adc resolution, in the unipolar input mode, assuming a pre-determined input polarity. if the input polarity is not known it is actua lly possible to determine the polarity first by using the bipolar input mode (with 9 bit resolution + 1 sign bit adc measurement). and once determined, set or clear the polarity reversal bit, as needed, for a succeeding 10 bit unipolar measurement. ? bits 4:3 ? res: reserved bits these bits are reserved bits in the attiny25/45/85 and will always read as zero. ? bits 2:0 ? adts[2:0]: adc auto trigger source if adate in adcsra is written to one, the value of these bits selects which source will trigger an adc conversion. if adate is cleared, the adts[2:0] settings will have no effect. a conver- sion will be triggered by the rising edge of the selected in terrupt flag. note th at switching from a trigger source that is cleared to a trigger sour ce that is set, will generate a positive edge on the trigger signal. if aden in adcsra is set, this will start a conversion. switching to free running mode (adts[2:0]=0) will not cause a trigger event, even if t he adc interrupt flag is set . 17.13.5 didr0 ? digital input disable register 0 ? bits 5:2 ? adc3d:adc0d: adc[3: 0] digital input disable when this bit is written logic one, the digita l input buffer on the corresponding adc pin is dis- abled. the corresponding pin register bit will always read as zero when this bit is set. when an analog signal is applied to the adc[3:0] pin and the digital input from this pin is not needed, this bit should be written logic one to reduce power consumption in the digital input buffer. table 17-6. adc auto trigger source selections adts2 adts1 adts0 trigger source 0 0 0 free running mode 0 0 1 analog comparator 0 1 0 external interrupt request 0 0 1 1 timer/counter0 compare match a 1 0 0 timer/counter0 overflow 1 0 1 timer/counter0 compare match b 1 1 0 pin change interrupt request bit 76543210 0x14 ? ? adc0d adc2d adc3d adc1d ain1d ain0d didr0 read/write r r r/w r/w r/w r/w r/w r/w initial value00000000 143 2586n?avr?04/11 attiny25/45/85 18. debugwire on-chip debug system 18.1 features ? complete program flow control ? emulates all on-chip functions, both digital and an alog , except reset pin ? real-time operation ? symbolic debugging support (both at c and assembler source level, or for other hlls) ? unlimited number of prog ram break points (using software break points) ? non-intrusive operation ? electrical characteristics identical to real device ? automatic configuration system ? high-speed operation ? programming of non-volatile memories 18.2 overview the debugwire on-chip debug system uses a one-wire, bi-directional interface to control the program flow, execute avr instructions in the cpu and to program the different non-volatile memories. 18.3 physical interface when the debugwire enable (dwen) fuse is programmed and lock bits are unprogrammed, the debugwire system within the target device is activated. the reset port pin is configured as a wire-and (open-drain) bi-directional i/o pin with pull-up enabled and becomes the commu- nication gateway between target and emulator. figure 18-1 shows the schematic of a target mcu, with debugwire enabled, and the emulator connector. the system clock is not affected by debugwire and will always be the clock source selected by the cksel fuses. figure 18-1. the debugwire setup dw gnd dw(reset) vcc 1.8 - 5.5v 144 2586n?avr?04/11 attiny25/45/85 when designing a system where debugwire will be used, the following must be observed: ? pull-up resistor on the dw/(reset) line must be in the ra nge of 10k to 20 k . however, the pull-up resistor is optional. ? connecting the reset pin directly to v cc will not work. ? capacitors inserted on the reset pin must be disconnected when using debugwire. ? all external reset sources must be disconnected. 18.4 software break points debugwire supports program memory break points by the avr break instruction. setting a break point in avr studio ? will insert a break instruction in the program memo ry. the instruc- tion replaced by the break instru ction will be stored. when program execution is continued, the stored instruction will be execut ed before continuing from the program memory. a break can be inserted manually by putting the break instruction in the program. the flash must be re-programmed each time a break point is changed. this is automatically handled by avr studio th rough the debugwire inte rface. the use of brea k points will therefore reduce the flash data retention. devices used for debugging purposes should not be shipped to end customers. 18.5 limitations of debugwire the debugwire communication pin (dw) is physica lly located on the same pin as external reset (reset). an external reset source is therefore not supported when the debugwire is enabled. the debugwire system accurately emulates all i/ o functions when running at full speed, i.e., when the program in the cpu is running. when the cpu is stopped, care must be taken while accessing some of the i/o registers via the debugger (avr studio). see the debugwire docu- mentation for detailed description of the limitations. the debugwire interface is asynchronous, whic h means that the debugger needs to synchro- nize to the system clock. if the system clock is changed by software (e.g . by writing clkps bits) communication via debugwire may fail. also, clock frequencies below 100khz may cause com- munication problems. a programmed dwen fuse enable s some parts of the clock system to be running in all sleep modes. this will increase the power consumption while in sleep. thus, the dwen fuse should be disabled when debugwire is not used. 18.6 register description the following section describes the registers used with the debugwire. 18.6.1 dwdr ? debugwire data register the dwdr register provides a communication channel from the running program in the mcu to the debugger. this register is only accessible by the debugwire and can therefore not be used as a general purpose register in the normal operations. bit 76543210 0x22 dwdr7 dwdr6 dwdr5 dwdr4 dwdr3 dwdr2 dwdr1 dwdr0 dwdr read/write r/w r/w r/w r/w r/w r/w r/w r/w initial value00000000 145 2586n?avr?04/11 attiny25/45/85 19. self-programming the flash the device provides a self-programming me chanism for downloading and uploading program code by the mcu itself. the self-programming ca n use any available data interface and associ- ated protocol to read code and write (program) that code into the program memory. the spm instruction is disabled by default but it ca n be enabled by programming the selfprgen fuse (to ?0?). the program memory is updated in a page by page fashion. before programming a page with the data stored in the temporary page buffer, the page must be erased. the temporary page buf- fer is filled one word at a time using spm and the buffer can be filled either before the page erase command or between a page erase and a page write operation: alternative 1, fill the bu ffer before a page erase ? fill temporary page buffer ? perform a page erase ? perform a page write alternative 2, fill the bu ffer after page erase ? perform a page erase ? fill temporary page buffer ? perform a page write if only a part of the page needs to be changed, the rest of the page must be stored (for example in the temporary page buffer) before the erase, and then be re-written. when using alternative 1, the boot loader provides an effective read-modify-write feature which allows the user software to first read the page, do the necessary changes, and then write back the modified data. if alter- native 2 is used, it is not possible to read the old data while loading since the page is already erased. the temporary page buffer can be accessed in a random sequence. it is essential that the page address used in both the page erase and page write operation is addressing the same page. 19.1 performing page erase by spm to execute page erase, set up the address in the z-pointer, write ?00000011? to spmcsr and execute spm within four clock cycles after writing spmcsr. the data in r1 and r0 is ignored. the page address must be written to pcpage in the z-register. other bits in the z-pointer will be ignored during this operation. note: the cpu is halted during the page erase operation. 19.2 filling the temporar y buffer (page loading) to write an instruction word, set up the address in the z-pointer and data in r1:r0, write ?00000001? to spmcsr and execute spm within four clock cycles after writing spmcsr. the content of pcword in the z-register is used to address the data in the temporary buffer. the temporary buffer will auto-erase after a page write operation or by writing the ctpb bit in spmcsr. it is also erased after a system reset. note that it is not possible to write more than one time to each address without erasing the temporary buffer. 146 2586n?avr?04/11 attiny25/45/85 if the eeprom is written in the middle of an spm page load operation, all data loaded will be lost. 19.3 performing a page write to execute page write, set up the address in the z-pointer, write ?00000101? to spmcsr and execute spm within four clock cycles after writing spmcsr. the data in r1 and r0 is ignored. the page address must be written to pcpage. other bits in the z-pointer must be written to zero during this operation. note: the cpu is halted during the page write operation. 19.4 addressing the flash during self-programming the z-pointer is used to address the spm commands. since the flash is organized in pages (see table 20-8 on page 154 ), the program counter can be treated as having two different sections. one sect ion, consisting of the least significant bits, is addressing the words within a page, while the most significant bits are addressing the pages. this is shown in figure 19-1 . note that the page erase and page write operations are addressed independently. therefore it is of major importance that the software addresses the same page in both the page erase and page write operation. the lpm instruction uses the z-pointer to store the address. since this instruction addresses the flash byte-by-byte, also the lsb (bit z0) of the z-pointer is used. figure 19-1. addressing the flash during spm (1) note: 1. the different variables used in figure 19-1 are listed in table 20-8 on page 154 . bit 1514131211109 8 zh (r31) z15 z14 z13 z12 z11 z10 z9 z8 zl (r30)z7z6z5z4z3z2z1z0 76543210 program memory 0 1 15 z - register bit 0 zpagemsb word address within a page page address within the flash zpcmsb instruction word pag e pcword[pagemsb:0]: 00 01 02 pageend pag e pcword pcpage pcmsb pagemsb program counter 147 2586n?avr?04/11 attiny25/45/85 19.5 eeprom write prevent s writing to spmcsr note that an eeprom write oper ation will block all software progra mming to flash. reading the fuses and lock bits from software will also be prevented during the eeprom write operation. it is recommended that the user checks the status bit (eepe) in the eecr register and verifies that the bit is cleared before writing to the spmcsr register. 19.6 reading lock, fuse and signat ure data from software it is possible to read fuse and lock bits from firmware. in addition, firmware can also read data from the device signature imprint table (see page 153 ). note: fuse and lock bits that are programmed, will be read as zero. fuse and lock bits that are unpro- grammed, will be read as one. 19.6.1 reading lock bits from firmware issuing an lpm instruction within three cpu cycles after rflb and selfprgen bits have been set in spmcsr will return lock bit values in the destination register. the rflb and self- prgen bits automatically clear upon completion of reading the lock bits, or if no lpm instruction is executed within three cpu cycles, or if no spm instruction is executed within four cpu cycles. when rflb and selfprgen are cleared lpm functions normally. to read the lock bits, follow the below procedure: 1. load the z-pointer with 0x0001. 2. set rflb and selfprgen bits in spmcsr. 3. issue an lpm instruction within three clock cycles. 4. read the lock bits from the lpm destination register. if successful, the contents of the destination register are as follows. see section ?program and data memory lock bits? on page 151 for more information. 19.6.2 reading fuse bits from firmware the algorithm for reading fuse byte s is similar to the one described above for reading lock bits, only the addresses are different. to read the fuse low byte (flb), follow the below procedure: 1. load the z-pointer with 0x0000. 2. set rflb and selfprgen bits in spmcsr. 3. issue an lpm instruction within three clock cycles. 4. read the flb from the lpm destination register. if successful, the contents of the destination register are as follows. refer to table 20-5 on page 153 for a detailed description and mapping of the fuse low byte. bit 76543210 rd ??????lb2lb1 bit 76543210 rd flb7 flb6 flb5 flb4 flb3 flb2 flb1 flb0 148 2586n?avr?04/11 attiny25/45/85 to read the fuse high byte (fhb), simply repl ace the address in the z-pointer with 0x0003 and repeat the procedure above. if successful, the contents of the destination register are as follows. refer to table 20-4 on page 152 for detailed description and mapping of the fuse high byte. to read the fuse extended byte (feb), replace the address in the z-pointer with 0x0002 and repeat the previous procedure. if successful, t he contents of the destination register are as follows. refer to table 20-3 on page 152 for detailed description and mapping of the fuse extended byte. 19.6.3 reading device signature imprint table from firmware to read the contents of the device signature imprint table, follow the below procedure: 1. load the z-pointer with the table index. 2. set rsig and spmen bits in spmcsr. 3. issue an lpm instruction within three clock cycles. 4. read table data from the lpm destination register. see program example below. note: 1. see ?code examples? on page 6 . if successful, the contents of the destination register are as described in section ?device signa- ture imprint table? on page 153 . bit 76543210 rd fhb7 fhb6 fhb5 fhb4 fhb3 fhb2 fhb1 fhb0 bit 76543210 rd feb7 feb6 feb5 feb4 feb3 feb2 feb1 feb0 assembly code example (1) dsit_read: ; uses z-pointer as table index ldi zh, 0 ldi zl, 1 ; preload spmcsr bits into r16, then write to spmcsr ldi r16, (1< 150 2586n?avr?04/11 attiny25/45/85 ? bit 4 ? ctpb: clear temporary page buffer if the ctpb bit is writte n while filling the temporary page bu ffer, the temporary page buffer will be cleared and the da ta will be lost. ? bit 3 ? rflb: read fuse and lock bits an lpm instruction within three cycles after rflb and spmen are set in the spmcsr register, will read either the lock bits or t he fuse bits (depending on z0 in the z-pointer) in to the destina- tion register. see ?eeprom write preven ts writing to spmcsr? on page 147 for details. ? bit 2 ? pgwrt: page write if this bit is written to one at the same time as spmen, the next spm instruction within four clock cycles executes page write, with the data stored in the temporary buffer. the page address is taken from the high part of the z-pointer. the data in r1 and r0 are ignored. the pgwrt bit will auto-clear upon co mpletion of a page write, or if no spm instruction is ex ecuted within four clock cycles. the cpu is halted during the entire page write operation. ? bit 1 ? pgers: page erase if this bit is written to one at the same time as spmen, the next spm instruction within four clock cycles executes page erase. the page address is taken from the high part of the z-pointer. the data in r1 and r0 are ignored. the pgers bi t will auto-clear upon comp letion of a page erase, or if no spm instruction is executed within four clock cycles. the cpu is halted during the entire page write operation. ? bit 0 ? spmen: store program memory enable this bit enables the spm instruction for the next four clock cycles. if set to one together with rsig, ctpb, rflb, pgwrt or pgers, the follo wing lpm/spm instructi on will have a special meaning, as described elsewhere. if only spmen is written, the following spm inst ruction will store the value in r1:r0 in the tem- porary page buffer addressed by the z-pointer. the lsb of the z-pointer is ignored. the spmen bit will auto-clear upon completion of an spm instruction, or if no spm instruction is executed within four clock cycles. during page erase and page write, the spmen bit remains high until the operation is completed. 151 2586n?avr?04/11 attiny25/45/85 20. memory programming this section describes the different methods for programming the attiny25/45/85 memories. 20.1 program and data memory lock bits attiny25/45/85 provides two lock bits which can be left unprogrammed (?1?) or can be pro- grammed (?0?) to obtain the additional security listed in table 20-2 . lock bits can be erased to ?1? with the chip erase command, only. program memory can be read out via the debugwire interface when the dwen fuse is pro- grammed, even if the lock bits are set. thus, when lock bit security is required debugwire should always be disabled (by clearing the dwen fuse). note: 1. ?1? means unprogrammed, ?0? means programmed notes: 1. program the fuse bits before programming the lb1 and lb2. 2. ?1? means unprogrammed, ?0? means programmed lock bits can also be read by device firmware. see section ?reading lock, fuse and signature data from software? on page 147 . table 20-1. lock bit byte (1) lock bit bit no description default value 7 ? 1 (unprogrammed) 6 ? 1 (unprogrammed) 5 ? 1 (unprogrammed) 4 ? 1 (unprogrammed) 3 ? 1 (unprogrammed) 2 ? 1 (unprogrammed) lb2 1 lock bit 1 (unprogrammed) lb1 0 lock bit 1 (unprogrammed) table 20-2. lock bit protection modes (1)(2) memory lock bits protection type lb mode lb2 lb1 1 1 1 no memory lock features enabled. 210 further programming of the flash and eeprom is disabled in high-voltage and serial programming mode. the fuse bits are locked in both serial and high-voltage programming mode. (1) debugwire is disabled. 300 further programming and verifica tion of the flash and eeprom is disabled in high-voltage and serial programming mode. the fuse bits are locked in both serial and high-voltage programming mode. (1) debugwire is disabled. 152 2586n?avr?04/11 attiny25/45/85 20.2 fuse bytes attiny25/45/85 has three fuse bytes, as described in table 20-3 , table 20-4 , and table 20-5 . note that fuses are read as logical zero, ?0?, when programmed. notes: 1. enables spm instruction. see ?self-programming the flash? on page 145 . notes: 1. controls use of reset pin. see ?alternate functions of port b? on page 62 . 2. after this fuse has been programmed device can be programmed via high-voltage serial mode, only. 3. must be unprogrammed when lock bit security is required. see ?program and data memory lock bits? on page 151. 4. this fuse is not accessible in spi programming mode. 5. see ?wdtcr ? watchdog timer control register? on page 47 for details. 6. see table ?bodlevel fuse coding. ta = -40 c to +85 c? on page 171 . table 20-3. fuse extended byte fuse high byte bit no de scription default value 7 - 1 (unprogrammed) 6 - 1 (unprogrammed) 5 - 1 (unprogrammed) 4 - 1 (unprogrammed) 3 - 1 (unprogrammed) 2 - 1 (unprogrammed) 1 - 1 (unprogrammed) selfprgen (1) 0 self-programming enabled 1 (unprogrammed) table 20-4. fuse high byte fuse high byte bit no de scription default value rstdisbl (1) (2) 7 external reset disabled 1 (unprogrammed) dwen (1) (2) (3) 6 debugwire enabled 1 (unprogrammed) spien (4) 5 serial program and data download enabled 0 (programmed) (spi prog. enabled) wdton (5) 4 watchdog timer always on 1 (unprogrammed) eesave 3 eeprom preserves chip erase 1 (unprogrammed) (eeprom not preserved) bodlevel2 (6) 2 brown-out detector trig ger level 1 (unprogrammed) bodlevel1 (6) 1 brown-out detector trig ger level 1 (unprogrammed) bodlevel0 (6) 0 brown-out detector trig ger level 1 (unprogrammed) 153 2586n?avr?04/11 attiny25/45/85 notes: 1. see ?system clock prescaler? on page 31 for details. 2. allows system clock to be output on pin. see ?clock output buffer? on page 32 for details. 3. the default value gives maximum start-up time for the default clock source. see table 6-7 on page 28 for details. 4. the default setting selects internal, 8 mhz rc oscillator. see table 6-6 on page 28 for details. note that fuse bits are locked if lock bit 1 (lb1) is programmed. fuse bits should be pro- grammed before lock bits. the status of fuse bits is not affected by chip erase. lock bits can also be read by device firmware. see section ?reading lock, fuse and signature data from software? on page 147 . 20.2.1 latching of fuses fuse values are latched when the device enters programming mode and changes to fuse values will have no effect until the part leaves programming mode. this does not apply to the eesave fuse which takes effect once it is programmed. fuses are also latched on power-up. 20.3 device signature imprint table the device signature imprint table is a dedicated memory area used for storing miscellaneous device information, such as the device signatur e and oscillator calibrat ion data. most of this memory segment is reserved for internal use, as outlined in table 20-6 . notes: 1. see section ?signature bytes? for more information. 2. see section ?calibration bytes? for more information. table 20-5. fuse low byte fuse low byte bit no de scription default value ckdiv8 (1) 7 clock divided by 8 0 (programmed) ckout (2) 6 clock output enabled 1 (unprogrammed) sut1 (3) 5 start-up time setting 1 (unprogrammed) (3) sut0 (3) 4 start-up time sett ing 0 (programmed) (3) cksel3 (4) 3 clock source setting 0 (programmed) (4) cksel2 (4) 2 clock source setting 0 (programmed) (4) cksel1 (4) 1 clock source setting 1 (unprogrammed) (4) cksel0 (4) 0 clock source setting 0 (programmed) (4) table 20-6. contents of device signature imprint table. address high byte 0x00 signature byte 0 (1) 0x01 calibration data for internal oscillator at 8.0 mhz (2) 0x02 signature byte 1 (1) 0x03 calibration data for internal oscillator at 6.4 mhz (2) 0x04 signature byte 2 (1) 0x05 ... 0x2a reserved for internal use 154 2586n?avr?04/11 attiny25/45/85 20.3.1 signature bytes all atmel microcontrollers have a three-byte signature code which identifies the device. this code can be read in both serial and high-voltage programming mode, even when the device is locked. signature bytes can also be read by the device firmware. see section ?reading lock, fuse and signature data from software? on page 147 . the three signature bytes reside in a separate address space called the device signature imprint table. the signature data for attiny25/45/85 is given in table 20-7 . 20.3.2 calibration bytes the device signature imprint table of attiny25/45/85 contains two bytes of calibration data for the internal rc oscillator, as shown in table 20-6 on page 153 . in normal mode of operation the calibration data for 8 mhz operation is automatically fetched and written to the osccal register during reset. in attiny15 compatibility mode the calibration data for 6.4 mhz operation is used instead. this procedure guarantees the internal oscillator is always calib rated to the correct frequency. calibration bytes can also be read by the device firmware. see section ?reading lock, fuse and signature data from software? on page 147 . 20.4 page size table 20-7. device signature bytes part signature byte 0 signature byte 1 signature byte 0 attiny25 0x1e 0x91 0x08 attiny45 0x1e 0x92 0x06 attiny85 0x1e 0x93 0x0b table 20-8. no. of words in a page and no. of pages in the flash device flash size page size pcword no. of pages pcpage pcmsb at t i n y 2 5 1k words (2k bytes) 16 words pc[3:0] 64 pc[9:4] 9 at t i n y 4 5 2k words (4k bytes) 32 words pc[4:0] 64 pc[10:5] 10 at t i n y 8 5 4k words (8k bytes) 32 words pc[4:0] 128 pc[11:5] 11 table 20-9. no. of words in a page and no. of pages in the eeprom device eeprom size page size pcword no. of pages pcpage eeamsb attiny25 128 bytes 4 bytes eea[1:0] 32 eea[6:2] 6 attiny45 256 bytes 4 bytes eea[1:0] 64 eea[7:2] 7 attiny85 512 bytes 4 bytes eea[1:0] 128 eea[8:2] 8 155 2586n?avr?04/11 attiny25/45/85 20.5 serial downloading both the flash and eeprom memo ry arrays can be programmed using the serial spi bus while reset is pulled to gnd. the serial interface consists of pins sck, mosi (input) and miso (out- put). see below. figure 20-1. serial programming and verify (1) notes: 1. if the device is clocked by the internal oscilla tor, it is no need to connect a clock source to the clki pin. after reset is set low, the programming enable instruction needs to be executed first before program/erase operations can be executed. note: in table 20-10 above, the pin mapping for spi programming is listed. not all parts use the spi pins dedicated for the internal spi interface. when programming the eeprom, an auto-erase cycle is built into the self-timed programming operation (in the serial mode only) and there is no need to first execute the chip erase instruction. the chip erase operation turns the content of every memory location in both the program and eeprom arrays into 0xff. depending on cksel fuses, a valid clock must be present. the minimum low and high periods for the serial clock (sck) input are defined as follows: low: > 2 cpu clock cycles for f ck < 12 mhz, 3 cpu clock cycles for f ck >= 12 mhz high: > 2 cpu clock cycles for f ck < 12 mhz, 3 cpu clock cycles for f ck >= 12 mhz table 20-10. pin mapping serial programming symbol pins i/o description mosi pb0 i serial data in miso pb1 o serial data out sck pb2 i serial clock vcc gnd sck miso mosi reset +1.8 - 5.5v 156 2586n?avr?04/11 attiny25/45/85 20.5.1 serial programming algorithm when writing serial data to the attiny25/45/85 , data is clocked on the rising edge of sck. when reading data from the at tiny25/45/85, data is clocked on the falling edge of sck. see figure 21-4 and figure 21-5 for timing details. to program and verify the attiny25/45/85 in the serial programming mode, the following sequence is recommended (see four byte instruction formats in table 20-12 ): 1. power-up sequence: apply power between v cc and gnd while reset and sck are set to ?0? ? in some systems, the programmer can not guarantee that sck is held low during power-up. in this case, reset must be given a positive pulse after sck has been set to '0'. the duration of the pulse must be at least t rst plus two cpu clock cycles. see table 21-4 on page 170 for minimum pulse width on reset pin, t rst 2. wait for at least 20 ms and enable serial programming by sending the programming enable serial instruction to pin mosi. 3. the serial programming instructions will no t work if the communic ation is out of syn- chronization. when in sync. the second byte (0x53), will echo back when issuing the third byte of the programming enable instruction. whether the echo is correct or not, all four bytes of the instruction must be transmitted. if the 0x53 did not echo back, give reset a positive pulse and issue a new programming enable command. 4. the flash is programmed one page at a time. the memory page is loaded one byte at a time by supplying the 5 lsb of the address and data together with the load program memory page instruction. to ensure correct loading of the page, the data low byte must be loaded before data high byte is applied for a given address. the program memory page is stored by loading the write program memory page instruction with the 6 msb of the address. if polling (rdy/bsy) is not used, the user must wait at least t wd_flash before issuing the next page. (see table 20-11 .) accessing the serial programming interface before the flash write operation completes can result in incorrect programming. 5. a: the eeprom array is programmed one byte at a time by supplying the address and data together with the appropriate write instruction. an eeprom memory location is first automatically erased before new data is written. if polling (rdy/bsy) is not used, the user must wait at least t wd_eeprom before issuing the next byte. (see table 20-11 .) in a chip erased device, no 0xffs in the data file(s) need to be programmed. b: the eeprom array is programmed one page at a time. the memory page is loaded one byte at a time by supplying the 2 lsb of the address and data together with the load eeprom memory page instruction. the eeprom me mory page is stored by loading the write eeprom memory page inst ruction with the 6 msb of the address. when using eeprom page access only by te locations loaded with the load eeprom memory page instruction is altered. the remaining locations remain unchanged. if poll- ing (rdy/bsy) is not used, the used must wait at least t wd_eeprom before issuing the next page (see table 20-9 ). in a chip erased device, no 0xff in the data file(s) need to be programmed. 6. any memory location can be verified by using the read instruction which returns the content at the selected address at serial output miso. 7. at the end of the programming session, reset can be set high to commence normal operation. 8. power-off sequence (if needed): set reset to ?1?. tu r n v cc power off. 157 2586n?avr?04/11 attiny25/45/85 20.5.2 serial programming instruction set table 20-12 on page 157 and figure 20-2 on page 158 describes the instruction set. table 20-11. minimum wait delay before writing the next flash or eeprom location symbol minimum wait delay t wd_flash 4.5 ms t wd_eeprom 4.0 ms t wd_erase 9.0 ms t wd_fuse 4.5 ms table 20-12. serial programming instruction set instruction/operation instruction format byte 1 byte 2 byte 3 byte4 programming enable $ac $53 $00 $00 chip erase (program memory/eeprom) $ac $80 $00 $00 poll rdy/bsy $f0 $00 $00 data byte out load instructions load extended address byte (1) $4d $00 extended adr $00 load program memory page, high byte $48 adr msb adr lsb high data byte in load program memory page, low byte $40 adr msb adr lsb low data byte in load eeprom memory page (page access) $c1 $00 0000 000aa data byte in read instructions read program memory, high byte $28 adr msb adr lsb high data byte out read program memory, low byte $20 adr msb adr lsb low data byte out read eeprom memory $a0 $00 00aa aaaa data byte out read lock bits $58 $00 $00 data byte out read signature byte $30 $00 0000 000aa data byte out read fuse bits $50 $00 $00 data byte out read fuse high bits $58 $08 $00 data byte out read extended fuse bits $50 $08 $00 data byte out read calibration byte $38 $00 $00 data byte out write instructions (6) write program memory page $4c adr msb adr lsb $00 write eeprom memory $c0 $00 00aa aaaa data byte in write eeprom memory page (page access) $c2 $00 00aa aa00 $00 write lock bits $ac $e0 $00 data byte in write fuse bits $ac $a0 $00 data byte in write fuse high bits $ac $a8 $00 data byte in write extended fuse bits $ac $a4 $00 data byte in 158 2586n?avr?04/11 attiny25/45/85 notes: 1. not all instructions are applicable for all parts. 2. a = address 3. bits are programmed ?0?, unprogrammed ?1?. 4. to ensure future compatibility, unused fuses and lock bits should be unprogrammed (?1?) . 5. refer to the correspondig section for fuse and lock bits, calibration and signature bytes and page size. 6. instructions accessing program memory use a word address. this address may be random within the page range. 7. see htt://www.atmel.com/avr for application notes regarding programming and programmers. if the lsb in rdy/bsy data byte out is ?1?, a pr ogramming operation is still pending. wait until this bit returns ?0? before the ne xt instruction is carried out. within the same page, the low data byte must be loaded prior to the high data byte. after data is loaded to the page buf fer, program the eeprom page, see figure 20-2 on page 158 . figure 20-2. serial programming instruction example byte 1 byte 2 byte 3 byte 4 adr lsb bit 15 b 0 serial programming instruction program memory/ eeprom memory page 0 page 1 page 2 page n-1 page buffer write program memory page/ write eeprom memory page load program memory page (high/low byte)/ load eeprom memory page (page access) byte 1 byte 2 byte 3 byte 4 bit 15 b 0 adr msb page offset page number ad r m ms sb a a adr r l lsb b 159 2586n?avr?04/11 attiny25/45/85 20.6 high-voltage serial programming this section describes how to program and verify flash program memory, eeprom data mem- ory, lock bits and fuse bits in the attiny25/45/85. figure 20-3. high-voltage serial programming the minimum period for the serial clock input (sci) during high-voltage serial programming is 220 ns. 20.7 high-voltage serial programming algorithm to program and verify the attiny25/45/85 in the high-voltage serial programming mode, the fol- lowing sequence is recommended (see instruction formats in table 20-16 ): table 20-13. pin name mapping signal name in high-voltage serial programming mode pin name i/o function sdi pb0 i serial data input sii pb1 i serial instruction input sdo pb2 o serial data output sci pb3 i serial clock input (min. 220ns period) table 20-14. pin values used to enter programming mode pin symbol value sdi prog_enable[0] 0 sii prog_enable[1] 0 sdo prog_enable[2] 0 vcc gnd s do s ii s di (re s et) +4.5 - 5.5v pb0 pb1 pb2 pb5 +11.5 - 12.5v pb 3 s ci 160 2586n?avr?04/11 attiny25/45/85 20.7.1 enter high-voltage serial programming mode the following algorithm puts the device in high-voltage serial programming mode: 1. set prog_enable pins listed in table 20-14 to ?000?, reset pin and v cc to 0v. 2. apply 4.5 - 5.5v between v cc and gnd. ensure that v cc reaches at least 1.8v within the next 20 s. 3. wait 20 - 60 s, and apply 11.5 - 12.5v to reset. 4. keep the prog_enable pins unchanged for at least 10 s after the high-voltage has been applied to ensure the prog_enable signature has been latched. 5. release the prog_enable[2] pin to avoid drive contention on the prog_enable[2]/sdo pin. 6. wait at least 300 s before giving any serial instructions on sdi/sii. 7. exit programming mode by power the device down or by bringing reset pin to 0v. if the rise time of the v cc is unable to fulfill the requiremen ts listed above, th e following alterna- tive algorithm can be used: 1. set prog_enable pins listed in table 20-14 to ?000?, reset pin and v cc to 0v. 2. apply 4.5 - 5.5v between v cc and gnd. 3. monitor v cc , and as soon as v cc reaches 0.9 - 1.1v, apply 11.5 - 12.5v to reset. 4. keep the prog_enable pins unchanged for at least 10 s after the high-voltage has been applied to ensure the prog_enable signature has been latched. 5. release the prog_enable[2] pin to avoid drive contention on the prog_enable[2]/sdo pin. 6. wait until v cc actually reaches 4.5 - 5.5v before giving any serial instructions on sdi/sii. 7. exit programming mode by power the device down or by bringing reset pin to 0v. 20.7.2 considerations for efficient programming the loaded command and address are retained in the device during programming. for efficient programming, the following should be considered. ? the command needs only be loaded once when writing or reading multiple memory locations. ? skip writing the data value 0xff that is the contents of the entire eeprom (unless the eesave fuse is programmed) and flash after a chip erase. ? address high byte needs only be loaded before programming or reading a new 256 word window in flash or 256 byte eeprom. this consideration also applies to signature bytes reading. table 20-15. high-voltage reset characteristics supply voltage reset pin high-voltage threshold minimum high-voltage period for latching prog_enable v cc v hvrst t hvrst 4.5v 11.5v 100 ns 5.5v 11.5v 100 ns 161 2586n?avr?04/11 attiny25/45/85 20.7.3 chip erase the chip erase will erase the flash and eeprom (1) memories plus lock bits. the lock bits are not reset until the program memory has been completely erased. the fuse bits are not changed. a chip erase must be performed before the flash and/or eeprom are re- programmed. note: 1. the eeprom memory is preserved duri ng chip erase if the eesave fuse is programmed. 1. load command ?chip erase? (see table 20-16 ). 2. wait after instr. 3 until sdo goes high for the ?chip erase? cycle to finish. 3. load command ?no operation?. 20.7.4 programming the flash the flash is organized in pages, see table 20-12 on page 157 . when programming the flash, the program data is latched into a page buffer. this allows one page of program data to be pro- grammed simultaneously. the following procedure describes how to program the entire flash memory: 1. load command ?write flash? (see table 20-16 ). 2. load flash page buffer. 3. load flash high address and program page. wait after instr. 3 until sdo goes high for the ?page programming? cycle to finish. 4. repeat 2 through 3 until the entire flash is programmed or until all data has been programmed. 5. end page programming by loading command ?no operation?. when writing or reading serial data to the atti ny25/45/85, data is clocked on the rising edge of the serial clock, see figure 20-5 , figure 21-6 and table 21-12 for details. figure 20-4. addressing the flash which is organized in pages program memory word address within a page page address within the flash instruction word pag e pcword[pagemsb:0]: 00 01 02 pageend pag e pcword pcpage pcmsb pagemsb program counter 162 2586n?avr?04/11 attiny25/45/85 figure 20-5. high-voltage serial programming waveforms 20.7.5 programming the eeprom the eeprom is organized in pages, see table 21-11 on page 175 . when programming the eeprom, the data is latc hed into a page buffer. this allo ws one page of data to be pro- grammed simultaneously. the programming algorithm for the eeprom data memory is as follows (refer to table 20-16 ): 1. load command ?write eeprom?. 2. load eeprom page buffer. 3. program eeprom page. wait after instr. 2 until sdo goes high for the ?page program- ming? cycle to finish. 4. repeat 2 through 3 until the entire eeprom is progra mmed or until all data has been programmed. 5. end page programming by loading command ?no operation?. 20.7.6 reading the flash the algorithm for reading the flash memory is as follows (refer to table 20-16 ): 1. load command "read flash". 2. read flash low and high bytes. the contents at the selected address are available at serial output sdo. 20.7.7 reading the eeprom the algorithm for reading the eeprom memory is as follows (refer to table 20-16 ): 1. load command ?read eeprom?. 2. read eeprom byte. the contents at the selected address are available at serial out- put sdo. 20.7.8 programming and reading the fuse and lock bits the algorithms for programming and reading the fuse low/high bits and lock bits are shown in table 20-16 . 20.7.9 reading the signature bytes and calibration byte the algorithms for reading the signature bytes and calibration byte are shown in table 20-16 . 20.7.10 power-off sequence set sci to ?0?. set reset to ?1?. turn v cc power off. msb msb msb lsb lsb lsb 012345678910 sdi pb0 sii pb1 sdo pb2 sci pb3 163 2586n?avr?04/11 attiny25/45/85 table 20-16. high-voltage serial programming instruction set for attiny25/45/85 instruction instruction format operation remarks instr.1/5 instr.2/6 instr.3 instr.4 chip erase sdi sii sdo 0_1000_0000_00 0_0100_1100_00 x_xxxx_xxxx_xx 0_0000_0000_00 0_0110_0100_00 x_xxxx_xxxx_xx 0_0000_0000_00 0_0110_1100_00 x_xxxx_xxxx_xx wait after instr.3 until sdo goes high for the chip erase cycle to finish. load ?write flash? command sdi sii sdo 0_0001_0000_00 0_0100_1100_00 x_xxxx_xxxx_xx enter flash programming code. load flash page buffer sdi sii sdo 0_ bbbb _ bbbb _00 0_0000_1100_00 x_xxxx_xxxx_xx 0_ eeee _ eeee _00 0_0010_1100_00 x_xxxx_xxxx_xx 0_ dddd _ dddd _00 0_0011_1100_00 x_xxxx_xxxx_xx 0_0000_0000_00 0_0111_1101_00 x_xxxx_xxxx_xx repeat after instr. 1 - 5 until the entire page buffer is filled or until all data within the page is filled. (2) sdi sii sdo 0_0000_0000_00 0_0111_1100_00 x_xxxx_xxxx_xx instr 5. load flash high address and program page sdi sii sdo 0_0000_000 a _00 0_0001_1100_00 x_xxxx_xxxx_xx 0_0000_0000_00 0_0110_0100_00 x_xxxx_xxxx_xx 0_0000_0000_00 0_0110_1100_00 x_xxxx_xxxx_xx wait after instr 3 until sdo goes high. repeat instr. 2 - 3 for each loaded flash page until the entire flash or all data is programmed. repeat instr. 1 for a new 256 byte page. (2) load ?read flash? command sdi sii sdo 0_0000_0010_00 0_0100_1100_00 x_xxxx_xxxx_xx enter flash read mode. read flash low and high bytes sdi sii sdo 0_ bbbb _ bbbb _00 0_0000_1100_00 x_xxxx_xxxx_xx 0_0000_000 a _00 0_0001_1100_00 x_xxxx_xxxx_xx 0_0000_0000_00 0_0110_1000_00 x_xxxx_xxxx_xx 0_0000_0000_00 0_0110_1100_00 q _ qqqq _ qqq x_xx repeat instr. 1, 3 - 6 for each new address. repeat instr. 2 for a new 256 byte page. sdi sii sdo 0_0000_0000_00 0_0111_1000_00 x_xxxx_xxxx_xx 0_0000_0000_00 0_0111_1100_00 p _ pppp _ ppp x_xx instr 5 - 6. load ?write eeprom? command sdi sii sdo 0_0001_0001_00 0_0100_1100_00 x_xxxx_xxxx_xx enter eeprom programming mode. load eeprom page buffer sdi sii sdo 0_00 bb _ bbbb _00 0_0000_1100_00 x_xxxx_xxxx_xx 0_ aaaa _ aaaa _00 0_0001_1100_00 x_xxxx_xxxx_xx 0_ eeee _ eeee _00 0_0010_1100_00 x_xxxx_xxxx_xx 0_0000_0000_00 0_0110_1101_00 x_xxxx_xxxx_xx repeat instr. 1 - 5 until the entire page buffer is filled or until all data within the page is filled. (3) sdi sii sdo 0_0000_0000_00 0_0110_1100_00 x_xxxx_xxxx_xx instr. 5 program eeprom page sdi sii sdo 0_0000_0000_00 0_0110_0100_00 x_xxxx_xxxx_xx 0_0000_0000_00 0_0110_1100_00 x_xxxx_xxxx_xx wait after instr. 2 until sdo goes high. repeat instr. 1 - 2 for each loaded eeprom page until the entire eeprom or all data is programmed. 164 2586n?avr?04/11 attiny25/45/85 write eeprom byte sdi sii sdo 0_ bbbb _ bbbb _00 0_0000_1100_00 x_xxxx_xxxx_xx 0_ aaaa _ aaaa _00 0_0001_1100_00 x_xxxx_xxxx_xx 0_ eeee _ eeee _00 0_0010_1100_00 x_xxxx_xxxx_xx 0_0000_0000_00 0_0110_1101_00 x_xxxx_xxxx_xx repeat instr. 1 - 6 for each new address. wait after instr. 6 until sdo goes high. (4) sdi sii sdo 0_0000_0000_00 0_0110_0100_00 x_xxxx_xxxx_xx 0_0000_0000_00 0_0110_1100_00 x_xxxx_xxxx_xx instr. 6 load ?read eeprom? command sdi sii sdo 0_0000_0011_00 0_0100_1100_00 x_xxxx_xxxx_xx enter eeprom read mode. read eeprom byte sdi sii sdo 0_ bbbb _ bbbb _00 0_0000_1100_00 x_xxxx_xxxx_xx 0_ aaaa _ aaaa _00 0_0001_1100_00 x_xxxx_xxxx_xx 0_0000_0000_00 0_0110_1000_00 x_xxxx_xxxx_xx 0_0000_0000_00 0_0110_1100_00 q _ qqqq _ qqq 0_00 repeat instr. 1, 3 - 4 for each new address. repeat instr. 2 for a new 256 byte page. write fuse low bits sdi sii sdo 0_0100_0000_00 0_0100_1100_00 x_xxxx_xxxx_xx 0_ a987 _ 6543 _00 0_0010_1100_00 x_xxxx_xxxx_xx 0_0000_0000_00 0_0110_0100_00 x_xxxx_xxxx_xx 0_0000_0000_00 0_0110_1100_00 x_xxxx_xxxx_xx wait after instr. 4 until sdo goes high. write a - 3 = ?0? to program the fuse bit. write fuse high bits sdi sii sdo 0_0100_0000_00 0_0100_1100_00 x_xxxx_xxxx_xx 0_ ihgf _ edcb _00 0_0010_1100_00 x_xxxx_xxxx_xx 0_0000_0000_00 0_0111_0100_00 x_xxxx_xxxx_xx 0_0000_0000_00 0_0111_1100_00 x_xxxx_xxxx_xx wait after instr. 4 until sdo goes high. write i - b = ?0? to program the fuse bit. write fuse extended bits sdi sii sdo 0_0100_0000_00 0_0100_1100_00 x_xxxx_xxxx_xx 0_0000_000 j _00 0_0010_1100_00 x_xxxx_xxxx_xx 0_0000_0000_00 0_0110_0110_00 x_xxxx_xxxx_xx 0_0000_0000_00 0_0110_1110_00 x_xxxx_xxxx_xx wait after instr. 4 until sdo goes high. write j = ?0? to program the fuse bit. write lock bits sdi sii sdo 0_0010_0000_00 0_0100_1100_00 x_xxxx_xxxx_xx 0_0000_00 21 _00 0_0010_1100_00 x_xxxx_xxxx_xx 0_0000_0000_00 0_0110_0100_00 x_xxxx_xxxx_xx 0_0000_0000_00 0_0110_1100_00 x_xxxx_xxxx_xx wait after instr. 4 until sdo goes high. write 2 - 1 = ?0? to program the lock bit. read fuse low bits sdi sii sdo 0_0000_0100_00 0_0100_1100_00 x_xxxx_xxxx_xx 0_0000_0000_00 0_0110_1000_00 x_xxxx_xxxx_xx 0_0000_0000_00 0_0110_1100_00 a _ 9876 _ 543 x_xx reading a - 3 = ?0? means the fuse bit is programmed. read fuse high bits sdi sii sdo 0_0000_0100_00 0_0100_1100_00 x_xxxx_xxxx_xx 0_0000_0000_00 0_0111_1010_00 x_xxxx_xxxx_xx 0_0000_0000_00 0_0111_1110_00 i _ hgfe _ dcb x_xx reading i - b = ?0? means the fuse bit is programmed. read fuse extended bits sdi sii sdo 0_0000_0100_00 0_0100_1100_00 x_xxxx_xxxx_xx 0_0000_0000_00 0_0110_1010_00 x_xxxx_xxxx_xx 0_0000_0000_00 0_0110_1110_00 x_xxxx_xxjx_xx reading j = ?0? means the fuse bit is programmed. read lock bits sdi sii sdo 0_0000_0100_00 0_0100_1100_00 x_xxxx_xxxx_xx 0_0000_0000_00 0_0111_1000_00 x_xxxx_xxxx_xx 0_0000_0000_00 0_0111_1100_00 x_xxxx_x 21 x_xx reading 2, 1 = ?0? means the lock bit is programmed. read signature bytes sdi sii sdo 0_0000_1000_00 0_0100_1100_00 x_xxxx_xxxx_xx 0_0000_00 bb _00 0_0000_1100_00 x_xxxx_xxxx_xx 0_0000_0000_00 0_0110_1000_00 x_xxxx_xxxx_xx 0_0000_0000_00 0_0110_1100_00 q _ qqqq _ qqq x_xx repeats instr 2 4 for each signature byte address. read calibration byte sdi sii sdo 0_0000_1000_00 0_0100_1100_00 x_xxxx_xxxx_xx 0_0000_0000_00 0_0000_1100_00 x_xxxx_xxxx_xx 0_0000_0000_00 0_0111_1000_00 x_xxxx_xxxx_xx 0_0000_0000_00 0_0111_1100_00 p _ pppp _ ppp x_xx load ?no operation? command sdi sii sdo 0_0000_0000_00 0_0100_1100_00 x_xxxx_xxxx_xx table 20-16. high-voltage serial programming instruction set for attiny25/45/85 (continued) instruction instruction format operation remarks instr.1/5 instr.2/6 instr.3 instr.4 165 2586n?avr?04/11 attiny25/45/85 notes: 1. a = address high bits, b = address low bits, d = data in high bits, e = data in low bits, p = data out high bits, q = data out low bits, x = don?t care, 1 = lock bit1, 2 = lock bit2, 3 = cksel0 fuse, 4 = cksel1 fuse, 5 = cksel2 fuse, 6 = cksel3 fuse, 7 = sut0 fuse, 8 = sut1 fuse, 9 = ckout fuse, a = ckdiv8 fuse, b = bodlevel0 fuse, c = bodlevel1 fuse, d = bodlevel2 fuse, e = eesave fuse, f = wdton fuse, g = spien fuse, h = dwen fuse, i = rstdisbl fuse, j = selfprgen fuse 2. for page sizes less than 256 words, parts of the address (bbbb_bbbb) will be parts of the page address. 3. for page sizes less than 256 bytes, parts of the address (bbbb_bbbb) will be parts of the page address. 4. the eeprom is written page-wise. but onl y the bytes that are loaded into the page are actually written to the eeprom. page-wise eeprom access is more efficient when multiple byte s are to be written to the same page. note that auto-erase of eeprom is not available in high-voltage serial programmi ng, only in spi programming. 166 2586n?avr?04/11 attiny25/45/85 21. electrical characteristics 21.1 absolute maximum ratings* 21.2 dc characteristics operating temperature.................................. -55 c to +125 c *notice: stresses beyond those listed under ?absolute maximum ratings? may cause permanent dam- age to the device. this is a stress rating only and functional operation of the device at these or other conditions beyond those indicated in the operational sections of th is specification is not implied. exposure to absolute maximum rating conditions for extended periods may affect device reliability. storage temperature ..................................... -65c to +150c voltage on any pin except reset with respect to ground ................................-0.5v to v cc +0.5v voltage on reset with respect to ground......-0.5v to +13.0v maximum operating voltage ............................................ 6.0v dc current per i/o pin ............................................... 40.0 ma dc current v cc and gnd pins................................ 200.0 ma table 21-1. dc characteristics. t a = -40 c to +85 c symbol parameter condition min. typ. (1) max. units v il input low-voltage, except xtal1 and reset pin v cc = 1.8v - 2.4v v cc = 2.4v - 5.5v -0.5 -0.5 0.2v cc (3) 0.3v cc (3) v v v ih input high-voltage, except xtal1 and reset pin v cc = 1.8v - 2.4v v cc = 2.4v - 5.5v 0.7v cc (2) 0.6v cc (2) v cc +0.5 v cc +0.5 v v v il1 input low-voltage, xtal1 pin, external clock selected v cc = 1.8v - 5.5v -0.5 0.1v cc (3) v v ih1 input high-voltage, xtal1 pin, external clock selected v cc = 1.8v - 2.4v v cc = 2.4v - 5.5v 0.8v cc (2) 0.7v cc (2) v cc +0.5 v cc +0.5 v v v il2 input low-voltage, reset pin v cc = 1.8v - 5.5v -0.5 0.2v cc (3) v v v ih2 input high-voltage, reset pin v cc = 1.8v - 5.5v 0.9v cc (2) v cc +0.5 v v il3 input low-voltage, reset pin as i/o v cc = 1.8v - 2.4v v cc = 2.4v - 5.5v -0.5 -0.5 0.2v cc (3) 0.3v cc (3) v v v ih3 input high-voltage, reset pin as i/o v cc = 1.8v - 2.4v v cc = 2.4v - 5.5v 0.7v cc (2) 0.6v cc (2) v cc +0.5 v cc +0.5 v v v ol output low-voltage, (4) port b (except reset ) (6) i ol = 10 ma, v cc = 5v i ol = 5 ma, v cc = 3v 0.6 0.5 v v v oh output high-voltage, (5) port b (except reset ) (6) i oh = -10 ma, v cc = 5v i oh = -5 ma, v cc = 3v 4.3 2.5 v v i il input leakage current i/o pin v cc = 5.5v, pin low (absolute value) < 0.05 1 a i ih input leakage current i/o pin v cc = 5.5v, pin high (absolute value) < 0.05 1 a 167 2586n?avr?04/11 attiny25/45/85 notes: 1. typical values at 25 c. 2. ?min? means the lowest value where t he pin is guaranteed to be read as high. 3. ?max? means the highest value where the pin is guaranteed to be read as low. 4. although each i/o port can sink more than the test conditions (10 ma at v cc = 5v, 5 ma at v cc = 3v) under steady state conditions (non-transient), th e following must be observed: 1] the sum of all iol, for a ll ports, should not exceed 60 ma. if iol exceeds the test condition, vol may exceed the related sp ecification. pins are not guar anteed to sink current greater than the listed test condition. 5. although each i/o port can source more than the test conditions (10 ma at v cc = 5v, 5 ma at v cc = 3v) under steady state conditions (non-transient), th e following must be observed: 1] the sum of all ioh, for a ll ports, should not exceed 60 ma. if ioh exceeds the test condition, voh ma y exceed the related specification. pins are not guaranteed to source current greater than the listed test condition. 6. the reset pin must tolerate high voltages when entering and operating in programming modes and, as a consequence, has a weak drive strength as compared to regular i/o pins. see figure 22-23 , figure 22-24 , figure 22-25 , and figure 22-26 (starting on page 189 ). 7. values are with external clock using methods described in ?minimizing power consumption? on page 37 . power reduction is enabled (prr = 0xff) and there is no i/o drive. 8. brown-out detection (bod) disabled. r rst reset pull-up resistor v cc = 5.5v, input low 30 60 k r pu i/o pin pull-up resistor v cc = 5.5v, input low 20 50 k i cc power supply current (7) active 1 mhz, v cc = 2v 0.3 0.55 ma active 4 mhz, v cc = 3v 1.5 2.5 ma active 8 mhz, v cc = 5v 5 8 ma idle 1 mhz, v cc = 2v 0.1 0.2 ma idle 4 mhz, v cc = 3v 0.35 0.6 ma idle 8 mhz, v cc = 5v 1.2 2 ma power-down mode (8) wdt enabled, v cc = 3v 10 a wdt disabled, v cc = 3v 2 a table 21-1. dc characteristics. t a = -40 c to +85 c (continued) symbol parameter condition min. typ. (1) max. units 168 2586n?avr?04/11 attiny25/45/85 21.3 speed figure 21-1. maximum frequency vs. v cc figure 21-2. maximum frequency vs. v cc 10 mhz 4 mhz 1.8v 2.7v 5.5v safe operating area 20 mhz 10 mhz 2.7v 4.5v 5.5v safe operating area 169 2586n?avr?04/11 attiny25/45/85 21.4 clock characteristics 21.4.1 calibrated internal rc oscillator accuracy it is possible to manua lly calibrate the internal oscillator to be more accu rate than def ault factory calibration. please note that th e oscillator frequency depends on temperature and voltage. volt- age and temperature characteristics can be found in figure 22-40 on page 198 and figure 22- 41 on page 198 . notes: 1. accuracy of oscillator frequency at calibra tion point (fixed temperature and fixed voltage). 2. attiny25/v, only: 6.4 mhz in attiny15 compatibility mode. 3. voltage range for attiny25v/45v/85v. 4. voltage range for attiny25/45/85. 21.4.2 external clock drive figure 21-3. external clock drive waveforms table 21-2. calibration accuracy of internal rc oscillator calibration method target frequency v cc temperature accuracy at given voltage & temperature (1) factory calibration 8.0 mhz (2) 3v 25 c10% user calibration fixed frequency within: 6 ? 8 mhz fixed voltage within: 1.8v - 5.5v (3) 2.7v - 5.5v (4) fixed temperature within: -40 c to +85 c 1% v il1 v ih1 table 21-3. external clock drive characteristics symbol parameter v cc = 1.8 - 5.5v v cc = 2.7 - 5.5v v cc = 4.5 - 5.5v units min. max. min. max. min. max. 1/t clcl clock frequency 0 4 0 10 0 20 mhz t clcl clock period 250 100 50 ns t chcx high time 100 40 20 ns t clcx low time 100 40 20 ns t clch rise time 2.0 1.6 0.5 s t chcl fall time 2.0 1.6 0.5 s t clcl change in period from one clock cycle to the next 2 2 2 % 170 2586n?avr?04/11 attiny25/45/85 21.5 system and reset characteristics note: 1. values are guidelines only. two versions of power-on reset have been implemented, as follows. 21.5.1 standard power-on reset this implementation of power-on reset existed in early versions of attiny25/45/85. the table below describes the characteristics of this power-on reset and it is valid for the following devices, only: ? attiny25, revision d, and older ? attiny45, revision f, and older ? attiny85, revision b, and newer note: revisions are marked on the package (packages 8p3 and 8s2: bottom, package 20m1: top) note: 1. values are guidelines, only 2. threshold where device is released from reset when voltage is rising 3. the power-on reset will not work unless the supply voltage has been below v poa table 21-4. reset, brown-out and internal voltage characteristics symbol parameter condition min (1) typ (1) max (1) units v rst reset pin threshold voltage v cc = 3v 0.2 v cc 0.9 v cc v t rst minimum pulse width on reset pin v cc = 3v 2.5 s v hyst brown-out detector hysteresis 50 mv t bod min pulse width on brown-out reset 2s v bg bandgap reference voltage v cc = 5.5v t a = 25c 1.0 1.1 1.2 v t bg bandgap reference start-up time v cc = 2.7v t a = 25c 40 70 s i bg bandgap reference current consumption v cc = 2.7v t a = 25c 15 a table 21-5. characteristics of standard power-on reset. t a = -40 to +85 c symbol parameter min (1) typ (1) max (1) units v por release threshold of power-on reset (2) 0.7 1.0 1.4 v v poa activation threshold of power-on reset (3) 0.05 0.9 1.3 v sr on power-on slope rate 0.01 4.5 v/ms 171 2586n?avr?04/11 attiny25/45/85 21.5.2 enhanced power-on reset this implementation of power-on reset exists in newer versions of attiny25/45/85. the table below describes the characteristics of this power-on reset and it is valid for the following devices, only: ? attiny25, revision e, and newer ? attiny45, revision g, and newer ? attiny85, revision c, and newer note: 1. values are guidelines, only 2. threshold where device is released from reset when voltage is rising 3. the power-on reset will not work unless the supply voltage has been below v pot (falling) 21.6 brown-out detection note: 1. v bot may be below nominal minimum operating voltage for some devices. for devices where this is the case, the device is tested down to v cc = v bot during the production test. this guar- antees that a brown-out reset will occur before v cc drops to a voltage where correct operation of the microcontroll er is no longer guaranteed. table 21-6. characteristics of enhanced power-on reset. t a = -40 c to +85 c symbol parameter min (1) typ (1) max (1) units v por release threshold of power-on reset (2) 1.1 1.4 1.6 v v poa activation threshold of power-on reset (3) 0.6 1.3 1.6 v sr on power-on slope rate 0.01 v/ms table 21-7. bodlevel fuse coding. t a = -40 c to +85 c bodlevel[2:0] fuses min (1) typ (1) max (1) units 111 bod disabled 110 1.7 1.8 2.0 v 101 2.5 2.7 2.9 100 4.1 4.3 4.5 0xx reserved 172 2586n?avr?04/11 attiny25/45/85 21.7 adc characteristics note: 1. values are guidelines only. table 21-8. adc characteristics, single ended channels. t a = -40 c to +85 c symbol parameter condition min typ max units resolution 10 bits absolute accuracy (including inl, dnl, and quantization, gain and offset errors) v ref = 4v, v cc = 4v, adc clock = 200 khz 2lsb v ref = 4v, v cc = 4v, adc clock = 1 mhz 3lsb v ref = 4v, v cc = 4v, adc clock = 200 khz noise reduction mode 1.5 lsb v ref = 4v, v cc = 4v, adc clock = 1 mhz noise reduction mode 2.5 lsb integral non-linearity (inl) (accuracy after offset and gain calibration) v ref = 4v, v cc = 4v, adc clock = 200 khz 1lsb differential non-linearity (dnl) v ref = 4v, v cc = 4v, adc clock = 200 khz 0.5 lsb gain error v ref = 4v, v cc = 4v, adc clock = 200 khz 2.5 lsb offset error v ref = 4v, v cc = 4v, adc clock = 200 khz 1.5 lsb conversion time free running conversion 14 280 s clock frequency 50 1000 khz v in input voltage gnd v ref v input bandwidth 38.4 khz aref external reference voltage 2.0 v cc v v int internal voltage reference 1.0 1.1 1.2 v internal 2.56v reference (1) v cc > 3.0v 2.3 2.56 2.8 v r ref 32 k r ain analog input resistance 100 m adc output 0 1023 lsb 173 2586n?avr?04/11 attiny25/45/85 note: 1. values are guidelines only. table 21-9. adc characteristics, differential channels (unipolar mode). t a = -40 c to +85 c symbol parameter condition min typ max units resolution gain = 1x 10 bits gain = 20x 10 bits absolute accuracy (including inl, dnl, and quantization, gain and offset errors) gain = 1x v ref = 4v, v cc = 5v adc clock = 50 - 200 khz 10.0 lsb gain = 20x v ref = 4v, v cc = 5v adc clock = 50 - 200 khz 20.0 lsb integral non-linearity (inl) (accuracy after offset and gain calibration) gain = 1x v ref = 4v, v cc = 5v adc clock = 50 - 200 khz 4.0 lsb gain = 20x v ref = 4v, v cc = 5v adc clock = 50 - 200 khz 10.0 lsb gain error gain = 1x 10.0 lsb gain = 20x 15.0 lsb offset error gain = 1x v ref = 4v, v cc = 5v adc clock = 50 - 200 khz 3.0 lsb gain = 20x v ref = 4v, v cc = 5v adc clock = 50 - 200 khz 4.0 lsb conversion time free running conversion 70 280 s clock frequency 50 200 khz v in input voltage gnd v cc v v diff input differential voltage v ref /gain v input bandwidth 4 khz aref external reference voltage 2.0 v cc - 1.0 v v int internal voltage reference 1.0 1.1 1.2 v internal 2.56v reference (1) v cc > 3.0v 2.3 2.56 2.8 v r ref reference input resistance 32 k r ain analog input resistance 100 m adc conversion output 0 1023 lsb 174 2586n?avr?04/11 attiny25/45/85 note: 1. values are guidelines only. table 21-10. adc characteristics, differential channels (bipolar mode). t a = -40 c to +85 c symbol parameter condition min typ max units resolution gain = 1x 10 bits gain = 20x 10 bits absolute accuracy (including inl, dnl, and quantization, gain and offset errors) gain = 1x v ref = 4v, v cc = 5v adc clock = 50 - 200 khz 8.0 lsb gain = 20x v ref = 4v, v cc = 5v adc clock = 50 - 200 khz 8.0 lsb integral non-linearity (inl) (accuracy after offset and gain calibration) gain = 1x v ref = 4v, v cc = 5v adc clock = 50 - 200 khz 4.0 lsb gain = 20x v ref = 4v, v cc = 5v adc clock = 50 - 200 khz 5.0 lsb gain error gain = 1x 4.0 lsb gain = 20x 5.0 lsb offset error gain = 1x v ref = 4v, v cc = 5v adc clock = 50 - 200 khz 3.0 lsb gain = 20x v ref = 4v, v cc = 5v adc clock = 50 - 200 khz 4.0 lsb conversion time free running conversion 70 280 s clock frequency 50 200 khz v in input voltage gnd v cc v v diff input differential voltage v ref /gain v input bandwidth 4 khz aref external reference voltage 2.0 v cc - 1.0 v v int internal voltage reference 1.0 1.1 1.2 v internal 2.56v reference (1) v cc > 3.0v 2.3 2.56 2.8 v r ref reference input resistance 32 k r ain analog input resistance 100 m adc conversion output -512 511 lsb 175 2586n?avr?04/11 attiny25/45/85 21.8 serial programming characteristics figure 21-4. serial programming waveforms figure 21-5. serial programming timing note: 1. 2 t clcl for f ck < 12 mhz, 3 t clcl for f ck >= 12 mhz table 21-11. serial programming characteristics, t a = -40 c to +85 c, v cc = 1.8 - 5.5v (unless otherwise noted) symbol parameter min typ max units 1/t clcl oscillator frequency (v cc = 1.8 - 5.5v) 0 4 mhz t clcl oscillator period (v cc = 1.8 - 5.5v) 250 ns 1/t clcl oscillator frequency (v cc = 2.7 - 5.5v) 0 10 mhz t clcl oscillator period (v cc = 2.7 - 5.5v) 100 ns 1/t clcl oscillator frequency (v cc = 4.5v - 5.5v) 0 20 mhz t clcl oscillator period (v cc = 4.5v - 5.5v) 50 ns t shsl sck pulse width high 2 t clcl* ns t slsh sck pulse width low 2 t clcl* ns t ovsh mosi setup to sck high t clcl ns t shox mosi hold after sck high 2 t clcl ns t sliv sck low to miso valid 100 ns msb msb lsb lsb serial clock input (sck) serial data input (mosi) (miso) sample serial data output mosi miso sck t ovsh t shsl t slsh t shox t sliv 176 2586n?avr?04/11 attiny25/45/85 21.9 high-voltage serial pr ogramming characteristics figure 21-6. high-voltage serial programming timing table 21-12. high-voltage serial programming characteristics t a = 25 c 10%, v cc = 5.0v 10% (unless otherwise noted) symbol parameter min typ max units t shsl sci (pb3) pulse width high 125 ns t slsh sci (pb3) pulse width low 125 ns t ivsh sdi (pb0), sii (pb1) valid to sci (pb3) high 50 ns t shix sdi (pb0), sii (pb1) hold after sci (pb3) high 50 ns t shov sci (pb3) high to sdo (pb2) valid 16 ns t wlwh_pfb wait after instr. 3 for write fuse bits 2.5 ms sdi (pb0), sii (pb1) sdo (pb2) sci (pb3) t i v sh t shsl t slsh t shix t sho v 177 2586n?avr?04/11 attiny25/45/85 22. typical characteristics the data contained in this section is largely based on simulations and characterization of similar devices in the same process and design methods. thus, the data should be treated as indica- tions of how the part will behave. the following charts show typical behavior. t hese figures are not tested during manufacturing. all current consumption measurements are performed with all i/o pins configured as inputs and with internal pull-ups enabled. a sine wave generator with rail-to-rail output is used as clock source. the power consumption in power-down mode is independent of clock selection. the current consumption is a function of several factors such as: operating voltage, operating frequency, loading of i/o pins, switching rate of i/o pins, code executed and ambient tempera- ture. the dominating factors are operating voltage and frequency. the current drawn from capacitive loaded pins may be estimated (for one pin) as c l * v cc *f where c l = load capacitance, v cc = operating voltage and f = average switching frequency of i/o pin. the parts are characterized at frequencies higher than test limits. parts are not guaranteed to function properly at frequencies higher than the ordering code indicates. the difference between current consumption in power-down mode with watchdog timer enabled and power-down mode with watchdog timer disabled represents the differential cur- rent drawn by the watchdog timer. 22.1 active supply current figure 22-1. active supply current vs. low frequency (0.1 - 1.0 mhz) active supply current vs. low frequency 0.1 -1.0 mhz 5.5 v 5.0 v 4.5 v 4.0 v 3.3 v 2.7 v 1.8 v 0 0,2 0,4 0,6 0,8 1 1,2 0 0,1 0,2 0,3 0,4 0,5 0,6 0,7 0,8 0,9 1 frequency (mhz) i cc (ma) 178 2586n?avr?04/11 attiny25/45/85 figure 22-2. active supply current vs . frequency (1 - 20 mhz) figure 22-3. active supply current vs. v cc (internal rc o scillator, 8 mhz) active supply current vs. frequency 1 - 20 mhz 5.5 v 5.0 v 4.5 v 0 2 4 6 8 10 12 14 0 2 4 6 8 10 12 14 16 18 20 frequency (mhz) i cc (ma) 1.8v 2.7v 3.3v 4.0v active supply current vs. v cc internal rc oscillator, 8 mhz 85 ?c 25 ?c -40 ?c 0 1 2 3 4 5 6 7 1,5 2 2,5 3 3,5 4 4,5 5 5,5 v cc (v) i cc (ma) 179 2586n?avr?04/11 attiny25/45/85 figure 22-4. active supply current vs. v cc (internal rc o scillator, 1 mhz) figure 22-5. active supply current vs. v cc (internal rc o scillator, 128 khz) active supply current vs. v cc internal rc oscillator, 1 mhz 85 ?c 25 ?c -40 ?c 0 0,2 0,4 0,6 0,8 1 1,2 1,4 1,6 1,5 2 2,5 3 3,5 4 4,5 5 5,5 v cc (v) i cc (ma) active supply current vs. v cc internal rc oscillator, 128 khz 85 ?c 25 ?c -40 ?c 0 0,05 0,1 0,15 0,2 0,25 1,5 2 2,5 3 3,5 4 4,5 5 5,5 v cc (v) i cc (ma) 180 2586n?avr?04/11 attiny25/45/85 22.2 idle supply current figure 22-6. idle supply current vs. low frequency (0.1 - 1.0 mhz) figure 22-7. idle supply current vs. frequency (1 - 20 mhz) idle supply current vs. low frequency 0.1 - 1.0 mhz 5.5 v 5.0 v 4.5 v 4.0 v 3.3 v 2.7 v 1.8 v 0 0,05 0,1 0,15 0,2 0,25 0 0,1 0,2 0,3 0,4 0,5 0,6 0,7 0,8 0,9 1 frequency (mhz) i cc (ma) idle supply current vs. frequency 1 - 20 mhz 5.5 v 5.0 v 4.5 v 0 0,5 1 1,5 2 2,5 3 3,5 4 0 2 4 6 8 101214161820 frequency (mhz) i cc (ma) 1.8v 2.7v 3.3v 4.0v 181 2586n?avr?04/11 attiny25/45/85 figure 22-8. idle supply current vs. v cc (internal rc o scillator, 8 mhz)i figure 22-9. idle supply current vs. v cc (internal rc o scilllator, 1 mhz) idle supply current vs. v cc internal rc oscillator, 8 mhz 85 ?c 25 ?c -40 ?c 0 0,2 0,4 0,6 0,8 1 1,2 1,4 1,6 1,8 1,5 2 2,5 3 3,5 4 4,5 5 5,5 v cc (v) i cc (ma) idle supply current vs. v cc internal rc oscillator, 1 mhz 85 ?c 25 ?c -40 ?c 0 0,05 0,1 0,15 0,2 0,25 0,3 0,35 0,4 0,45 0,5 1,5 2 2,5 3 3,5 4 4,5 5 5,5 v cc (v) i cc (ma) 182 2586n?avr?04/11 attiny25/45/85 figure 22-10. idle supply current vs. v cc (internal rc o scillator, 128 khz) 22.3 supply current of i/o modules the tables and formulas below can be used to calculate the additional current consumption for the different i/o modules in active and idle mode. the enabling or disabling of the i/o modules are controlled by the power reduction register. see ?prr ? power reduction register? on page 39 for details. idle supply current vs. v cc internal rc oscillator, 128 khz 85 ?c 25 ?c -40 ?c 0 0,01 0,02 0,03 0,04 0,05 0,06 0,07 0,08 0,09 0,1 1,5 2 2,5 3 3,5 4 4,5 5 5,5 v cc (v) i cc (ma) table 22-1. additional current consumption for the different i/o modules (absolute values) prr bit typical numbers v cc = 2v, f = 1 mhz v cc = 3v, f = 4 mhz v cc = 5v, f = 8 mhz prtim1 45 ua 300 ua 1100 ua prtim0 5 ua 30 ua 110 ua prusi 5 ua 25 ua 100 ua pradc 15 ua 85 ua 340 ua table 22-2. additional current consumption (percentage) in active and idle mode prr bit additional current consumption compared to active wi th external clock (see figure 22-1 and figure 22-2 ) additional current consumption compared to idle with external clock (see figure 22-6 and figure 22-7 ) prtim1 20 % 80 % prtim0 2 % 10 % prusi 2 % 10 % pradc 5 % 25 % 183 2586n?avr?04/11 attiny25/45/85 it is possible to calculate the typical current consumption based on the numbers from table 22-2 for other v cc and frequency settings that listed in table 22-1 . 22.3.1 example calculate the expected current consumption in idle mode with usi, timer0, and adc enabled at v cc = 2.0v and f = 1 mhz. from table 22-2 on page 182 , third column, we see that we need to add 10% for the usi, 25% for the adc, and 10% for the timer0 module. reading from figure 22-9 , we find that the idle current consumption is ~ 0,18 ma at v cc = 2.0v and f = 1 mhz. the total current consumption in idle mode with usi, timer0, and adc enabled, gives: 22.4 power-down supply current figure 22-11. power-down supply current vs. v cc (watchdog timer disabled) i cc 018 ma , 101 , 025 , 01 , ++ + () 0261 ma , = power-down supply current vs. v cc watchdog timer disabled 85 c 25 c -40 c 0 0.2 0.4 0.6 0.8 1 1.2 1.4 1.5 2 2.5 3 3.5 4 4.5 5 5.5 v cc (v) i cc (ua) 184 2586n?avr?04/11 attiny25/45/85 figure 22-12. power-down supply current vs. v cc (watchdog timer enabled) 22.5 pin pull-up figure 22-13. i/o pin pull-up resistor current vs. input voltage (v cc = 1.8v) power-down supply current vs. v cc watchdog timer enabled 85 ?c 25 ?c -40 ?c 0 2 4 6 8 10 12 14 1.5 2 2.5 3 3.5 4 4.5 5 5.5 v cc (v) i cc (ua) i/o pin pull-up resistor current vs. input voltage v cc = 1.8v 85 ?c 25 ?c -40 ?c 0 10 20 30 40 50 60 0 0,2 0,4 0,6 0,8 1 1,2 1,4 1,6 1,8 2 v op (v) i op (ua ) 185 2586n?avr?04/11 attiny25/45/85 figure 22-14. i/o pin pull-up resistor current vs. input voltage (v cc = 2.7v) figure 22-15. i/o pin pull-up resistor current vs. input voltage (v cc = 5v) i/o pin pull-up resistor current vs. input voltage v cc = 2.7v 85 ?c 25 ?c -40 ?c 0 10 20 30 40 50 60 70 80 0 0,5 1 1,5 2 2,5 3 v op (v) i op (ua) i/o pin pull-up resistor current vs. input voltage v cc = 5v 85 ?c 25 ?c -40 ?c 0 20 40 60 80 100 120 140 160 0123456 v op (v) i op (ua) 186 2586n?avr?04/11 attiny25/45/85 figure 22-16. reset pull-up resistor curr ent vs. reset pin voltage (v cc = 1.8v) figure 22-17. reset pull-up resistor curr ent vs. reset pin voltage (v cc = 2.7v) reset pull-up resistor current vs. reset pin voltage v cc = 1.8v 85 ?c 25 ?c -40 ?c 0 5 10 15 20 25 30 35 40 0 0,2 0,4 0,6 0,8 1 1,2 1,4 1,6 1,8 2 v reset (v) i r eset (ua) reset pull-up resistor current vs. reset pin voltage v cc =2.7v 85 ?c 25 ?c -40 ?c 0 10 20 30 40 50 60 0 0,5 1 1,5 2 2,5 3 v reset (v) i reset (ua) 187 2586n?avr?04/11 attiny25/45/85 figure 22-18. reset pull-up resistor curr ent vs. reset pin voltage (v cc = 5v) 22.6 pin driver strength figure 22-19. i/o pin output voltage vs. sink current (v cc = 3v) reset pull-up resistor current vs. reset pin voltage v cc = 5v 85 ?c 25 ?c -40 ?c 0 20 40 60 80 100 120 0123456 v reset (v) i reset (ua) i/o pin output voltage vs. sink current v cc = 3v 85 25 -40 0 0,2 0,4 0,6 0,8 1 1,2 0 5 10 15 20 25 i ol (ma) v ol (v) 188 2586n?avr?04/11 attiny25/45/85 figure 22-20. i/o pin output voltage vs. sink current (v cc = 5v) figure 22-21. i/o pin output voltage vs. source current (v cc = 3v) i/o pin output voltage vs. sink current v cc = 5v 85 25 -40 0 0,1 0,2 0,3 0,4 0,5 0,6 0 5 10 15 20 25 i ol (ma) v ol (v) i/o pin output voltage vs. source current v cc = 3v 85 25 -40 0 0,5 1 1,5 2 2,5 3 3,5 0 5 10 15 20 25 i oh (ma) v oh (v) 189 2586n?avr?04/11 attiny25/45/85 figure 22-22. i/o pin output voltage vs. source current (v cc = 5v) figure 22-23. reset pin output voltage vs. sink current (v cc = 3v) i/o pin output voltage vs. source current v cc = 5v 85 25 -40 4,4 4,5 4,6 4,7 4,8 4,9 5 5,1 0 5 10 15 20 25 i oh (ma) v oh (v) reset as i/o pin output voltage vs. sink current v cc = 3v -45 c 0 c 85 c 0 0.5 1 1.5 00.511.522.53 i ol (ma) v ol (v) 190 2586n?avr?04/11 attiny25/45/85 figure 22-24. reset pin output voltage vs. sink current (v cc = 5v) figure 22-25. reset pin output voltage vs. source current (v cc = 3v) reset as i/o pin output voltage vs. sink current v cc = 5v -45 c 0 c 85 c 0 0.2 0.4 0.6 0.8 1 0 0.5 1 1.5 2 2.5 3 i ol (ma) v ol (v) reset as i/o pin output voltage vs. source current v cc = 3v -45 c 25 c 85 c 0 0.5 1 1.5 2 2.5 3 3.5 00.511.52 i oh (ma) v oh (v) 191 2586n?avr?04/11 attiny25/45/85 figure 22-26. reset pin output voltage vs. source current (v cc = 5v) 22.7 pin threshold and hysteresis figure 22-27. i/o pin input threshold voltage vs. v cc (v ih , io pin read as ?1?) reset as i/o pin output voltage vs. source current v cc = 5v -45 c 25 c 85 c 2.5 3 3.5 4 4.5 5 0 0.5 1 1.5 2 i oh (ma) v oh (v) i/o pin input threshold voltage vs. v cc vih, io pin read as '1' 85 ?c 25 ?c -40 ?c 0 0,5 1 1,5 2 2,5 3 1,5 2 2,5 3 3,5 4 4,5 5 5,5 v cc (v) threshold (v) 192 2586n?avr?04/11 attiny25/45/85 figure 22-28. i/o pin input threshold voltage vs. v cc (v il , io pin read as ?0?) figure 22-29. i/o pin input hysteresis vs. v cc i/o pin input threshold voltage vs. v cc vil, io pin read as '0' 85 ?c 25 ?c -40 ?c 0 0,5 1 1,5 2 2,5 3 1,5 2 2,5 3 3,5 4 4,5 5 5,5 v cc (v) threshold (v) 85 c 25 c -40 c 0 0,1 0,2 0,3 0,4 0,5 0,6 1,5 2 2,5 3 3,5 4 4,5 5 5,5 input hysteresis (v) v cc (v) i/o pin input hysteresis vs. vcc 193 2586n?avr?04/11 attiny25/45/85 figure 22-30. reset input threshold voltage vs. v cc (v ih , io pin read as ?1?) figure 22-31. reset input threshold voltage vs. v cc (v il , io pin read as ?0?) re s et input thre s hold voltage v s . vcc vih, io pin read a s '1' 8 5 c 25 c -40 c 0 0,5 1 1,5 2 2,5 1,5 2 2,5 33 ,544,555,5 vcc (v) thre s hold (v) re s et input thre s hold voltage v s . vcc vil, io pin read a s '0' 8 5 c 25 c -40 c 0 0,5 1 1,5 2 2,5 1,5 2 2,5 33 ,5 4 4,5 5 5,5 vcc (v) thre s hold (v) 194 2586n?avr?04/11 attiny25/45/85 figure 22-32. reset pin input hysteresis vs. v cc 22.8 bod threshold figure 22-33. bod threshold vs. temperature (bod level is 4.3v) reset pin input hysteresis vs. vcc 85 c 25 c -40 c 0 0,05 0,1 0,15 0,2 0,25 0,3 0,35 0,4 0,45 0,5 1,5 2 2,5 3 3,5 4 4,5 5 5,5 vcc (v) input hysteresis (v) bod thre s hold s v s . temperature ri s ing vcc f a lling vcc 4,26 4,2 8 4, 3 4, 3 2 4, 3 4 4, 3 6 4, 38 4,4 -50 -40 - 3 0 -20 -10 0 10 20 3 040506070 8 090100 temper a t u re (c) thre s hold (v) 195 2586n?avr?04/11 attiny25/45/85 figure 22-34. bod threshold vs. temperature (bod level is 2.7v) figure 22-35. bod threshold vs. temperature (bod level is 1.8v) bod thre s hold s v s . temperature ri s ing vcc f a lling vcc 2,6 8 2,7 2,72 2,74 2,76 2,7 8 2, 8 -50 -40 - 3 0 -20 -10 0 10 20 3 040506070 8 0 90 100 temper a t u re (c) thre s hold (v) bod thre s hold s v s . temperature ri s ing vcc f a lling vcc 1,795 1, 8 1, 8 05 1, 8 1 1, 8 15 1, 8 2 1, 8 25 1, 83 1, 83 5 1, 8 4 1, 8 45 1, 8 5 -50 -40 - 3 0 -20 -10 0 10 20 3 040506070 8 0 90 100 temper a t u re (c) thre s hold (v) 196 2586n?avr?04/11 attiny25/45/85 figure 22-36. bandgap voltage vs. supply voltage figure 22-37. bandgap voltage vs. temperature bandgap voltage vs. v cc 85 c 25 c -40 c 1 1,02 1,04 1,06 1,08 1,1 1,12 1,14 1,16 1,18 1,2 1,5 2 2,5 3 3,5 4 4,5 5 5,5 vcc (v) bandgap voltage (v) bandgap voltage vs. temperature 5 v 3 v 1.8 v 1 1,02 1,04 1,06 1,08 1,1 1,12 1,14 1,16 1,18 1,2 -40 -20 0 20 40 60 80 100 temperature bandgap voltage (v) 197 2586n?avr?04/11 attiny25/45/85 22.9 internal oscillator speed figure 22-38. watchdog oscillato r frequency vs. v cc figure 22-39. watchdog oscillator freq uency vs. temperature watchdog oscillator frequency vs. v cc 85 ?c 25 ?c -40 ?c 0,112 0,114 0,116 0,118 0,12 0,122 0,124 0,126 0,128 2 2,5 3 3,5 4 4,5 5 5,5 v cc (v) f rc (mhz) watchdog o s cillator frequency v s . temperature 5.5 v 4.0 v 3 . 3 v 2.7 v 1. 8 v 0,10 8 0,11 0,112 0,114 0,116 0,11 8 0,12 -40 - 3 0 -20 -10 0 10 20 3 040506070 8 090100 temper a t u re frc (mhz) 198 2586n?avr?04/11 attiny25/45/85 figure 22-40. calibrated 8 mhz rc osc illator frequency vs. v cc figure 22-41. calibrated 8 mhz rc oscillato r frequency vs. temperature calibrated 8 mhz rc oscillator frequency vs. v cc 85 ?c 25 ?c -40 ?c 7,5 7,6 7,7 7,8 7,9 8 8,1 8,2 1,5 2 2,5 3 3,5 4 4,5 5 5,5 v cc (v) f rc (m hz) calibrated 8 mhz rc oscillator frequency vs. temperature 5.0 v 3.0 v 7,7 7,75 7,8 7,85 7,9 7,95 8 8,05 8,1 8,15 -60 -40 -20 0 20 40 60 80 100 temperature f rc (mhz) 199 2586n?avr?04/11 attiny25/45/85 figure 22-42. calibrated 8 mhz rc oscillator frequency vs. osccal value figure 22-43. calibrated 1.6 mhz rc osc illator frequency vs. v cc calibrated 8 mhz rc oscillator frequency vs. osccal value 85 ?c 25 ?c -40 ?c 0 2 4 6 8 10 12 14 16 18 0 16 32 48 64 80 96 112 128 144 160 176 192 208 224 240 osccal (x1) f rc (mhz) calibrated 1.6 mhz rc oscillator frequency vs. v cc 85 ?c 25 ?c -40 ?c 1,4 1,45 1,5 1,55 1,6 1,65 1,5 2 2,5 3 3,5 4 4,5 5 5,5 v cc (v) f rc (mhz) 200 2586n?avr?04/11 attiny25/45/85 figure 22-44. calibrated 1.6 mhz rc oscillato r frequency vs. temperature figure 22-45. calibrated 1.6 mhz rc oscillator frequency vs. osccal value calibrated 1.6mhz rc oscillator frequency vs. temperature 5.0 v 3.0 v 1,5 1,52 1,54 1,56 1,58 1,6 1,62 1,64 -60 -40 -20 0 20 40 60 80 100 temperature f rc (mhz) calibrated 1.6 mhz rc oscillator frequency vs. osccal value 85 ?c 25 ?c -40 ?c 0 0,5 1 1,5 2 2,5 3 3,5 4 4,5 0 16 32 48 64 80 96 112 128 144 160 176 192 208 224 240 osccal (x1) f rc (mhz) 201 2586n?avr?04/11 attiny25/45/85 22.10 current consumption of peripheral units figure 22-46. brownout detector current vs. v cc figure 22-47. adc current vs. v cc (aref = av cc ) brownout detector current v s . vcc 8 5 c 25 c -40 c 0 5 10 15 20 25 3 0 1,5 2 2,5 33 ,5 4 4,5 5 5,5 vcc (v) icc ( u a) adc current v s . vcc aref = avcc 8 5 c 25 c -40 c 0 50 100 150 200 250 1,5 2 2,5 33 ,5 4 4,5 5 5,5 vcc (v) icc ( u a) 202 2586n?avr?04/11 attiny25/45/85 figure 22-48. analog comparator current vs. v cc figure 22-49. programming current vs. v cc analog comparator current v s . vcc 8 5 c 25 c -40 c 0 5 10 15 20 25 3 0 3 5 40 45 50 1,5 2 2,5 33 ,5 4 4,5 5 5,5 vcc (v) icc ( u a) programming current v s . vcc ext clk 8 5 c 25 c -40 c 0 2 4 6 8 10 12 1,5 2 2,5 33 ,5 4 4,5 5 5,5 vcc (v) icc (ma) 203 2586n?avr?04/11 attiny25/45/85 22.11 current consumption in reset and reset pulsewidth figure 22-50. reset supply current vs. v cc (0.1 - 1.0 mhz, excluding current through the reset pull-up) figure 22-51. reset supply current vs. v cc (1 - 20 mhz, excluding current through the reset pull-up) reset supply current vs. v cc 0.1 - 1.0 mhz, excluding current through the reset pullup 5.5 v 5.0 v 4.5 v 4.0 v 3.3 v 2.7 v 1.8 v 0 0,02 0,04 0,06 0,08 0,1 0,12 0,14 0,16 0 0,1 0,2 0,3 0,4 0,5 0,6 0,7 0,8 0,9 1 frequency (mhz) i cc (ma) reset supply current vs. v cc 1 - 20 mhz, excluding current through the reset pullup 5.5 v 5.0 v 4.5 v 0 0,5 1 1,5 2 2,5 0 2 4 6 8 101214161820 frequency (mhz) i cc (ma) 1.8v 2.7v 3.3v 4.0v 204 2586n?avr?04/11 attiny25/45/85 figure 22-52. minimum reset pulse width vs. v cc minimum reset pulse width vs. v cc 85 ?c 25 ?c -40 ?c 0 500 1000 1500 2000 2500 1,5 2 2,5 3 3,5 4 4,5 5 5,5 v cc (v) pulsewidth (ns) 205 2586n?avr?04/11 attiny25/45/85 23. register summary address name bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 page 0x3f sreg i t h s v n z c page 8 0x3e sph ? ? ? ? ? ? sp9 sp8 page 11 0x3d spl sp7 sp6 sp5 sp4 sp3 sp2 sp1 sp0 page 11 0x3c reserved ? 0x3b gimsk ? int0 pcie ? ? ? ? ? page 53 0x3a gifr ? intf0 pcif ? ? ? ? ? page 54 0x39 timsk ? ocie1a ocie1b ocie0a ocie0b toie1 toie0 ? pages 84 , 106 0x38 tifr ? ocf1a ocf1b ocf0a ocf0b tov1 tov0 ? page 84 0x37 spmcsr ? ? rsig ctpb rflb pgwrt pgers spmen page 149 0x36 reserved ? 0x35 mcucr bods pud se sm1 sm0 bodse isc01 isc00 pages 38 , 53 , 66 0x34 mcusr ? ? ? ? wdrf borf extrf porf page 46 , 0x33 tccr0b foc0a foc0b ? ? wgm02 cs02 cs01 cs00 page 82 0x32 tcnt0 timer/counter0 page 83 0x31 osccal oscillator calibration register page 32 0x30 tccr1 ctc1 pwm1a com1a1 com1a0 cs13 cs12 cs11 cs10 pages 92 , 103 0x2f tcnt1 timer/counter1 pages 94 , 105 0x2e ocr1a timer/counter1 output compare register a pages 94 , 105 0x2d ocr1c timer/counter1 output compare register c pages 95 , 106 0x2c gtccr tsm pwm1b com1b1 com1b0 foc1b foc1a psr1 psr0 pages 80 , 93 , 105 0x2b ocr1b timer/counter1 output compare register b page 95 0x2a tccr0a com0a1 com0a0 com0b1 com0b0 ? wgm01 wgm00 page 80 0x29 ocr0a timer/counter0 ? output compare register a page 83 0x28 ocr0b timer/counter0 ? output compare register b page 84 0x27 pllcsr lsm ? ? ? ? pcke plle plock pages 97 , 107 0x26 clkpr clkpce ? ? ? clkps3 clkps2 clkps1 clkps0 page 33 0x25 dt1a dt1ah3 dt1ah2 dt1ah1 dt 1ah0 dt1al3 dt1al2 dt1al1 dt1al0 page 110 0x24 dt1b dt1bh3 dt1bh2 dt1bh1 dt 1bh0 dt1bl3 dt1bl2 dt1bl1 dt1bl0 page 110 0x23 dtps1 - - - - - - dtps11 dtps10 page 109 0x22 dwdr dwdr[7:0] page 144 0x21 wdtcr wdif wdie wdp3 wdce wde wdp2 wdp1 wdp0 page 47 0x20 prr ? prtim1 prtim0 prusi pradc page 37 0x1f eearh eear8 page 20 0x1e eearl eear7 eear6 eear5 eear4 eear3 eear2 eear1 eear0 page 20 0x1d eedr eeprom data register page 20 0x1c eecr ? ? eepm1 eepm0 eerie eempe eepe eere page 21 0x1b reserved ? 0x1a reserved ? 0x19 reserved ? 0x18 portb ? ? portb5 portb4 portb3 portb2 portb1 portb0 page 66 0x17 ddrb ? ? ddb5 ddb4 ddb3 ddb2 ddb1 ddb0 page 66 0x16 pinb ? ? pinb5 pinb4 pinb3 pinb2 pinb1 pinb0 page 66 0x15 pcmsk ? ? pcint5 pcint4 pcint3 pcint2 pcint1 pcint0 page 54 0x14 didr0 ? ? adc0d adc2d adc3d adc1d ain1d ain0d pages 125 , 142 0x13 gpior2 general purpose i/o register 2 page 10 0x12 gpior1 general purpose i/o register 1 page 10 0x11 gpior0 general purpose i/o register 0 page 10 0x10 usibr usi buffer register page 118 0x0f usidr usi data register page 118 0x0e usisr usisif usioif usipf usi dc usicnt3 usicnt2 usicnt1 usicnt0 page 119 0x0d usicr usisie usioie usiwm1 usiwm0 usics1 usics0 usiclk usitc page 120 0x0c reserved ? 0x0b reserved ? 0x0a reserved ? 0x09 reserved ? 0x08 acsr acd acbg aco aci acie ? acis1 acis0 page 124 0x07 admux refs1 refs0 adlar refs2 mux3 mux2 mux1 mux0 page 138 0x06 adcsra aden adsc adate adif adie adps2 adps1 adps0 page 140 0x05 adch adc data register high byte page 141 0x04 adcl adc data register low byte page 141 0x03 adcsrb bin acme ipr ? ? adts2 adts1 adts0 pages 124 , 141 0x02 reserved ? 0x01 reserved ? 0x00 reserved ? 206 2586n?avr?04/11 attiny25/45/85 note: 1. for compatibility with future devices, reserved bits s hould be written to zero if accessed. reserved i/o memory addresse s should never be written. 2. i/o registers within the address range 0x00 - 0x1f are directly bit-accessible using the sbi and cbi instructions. in these registers, the value of single bits can be ch ecked by using the sbis and sbic instructions. 3. some of the status flags are cleared by writing a logical o ne to them. note that, unlike most other avrs, the cbi and sbi instructions will only operation the specified bit, and can theref ore be used on registers contai ning such status flags. the cbi and sbi instructions work wit h registers 0x00 to 0x1f only. 207 2586n?avr?04/11 attiny25/45/85 24. instruction set summary mnemonics operands description operation flags #clocks arithmetic and logic instructions add rd, rr add two registers rd rd + rr z,c,n,v,h 1 adc rd, rr add with carry two registers rd rd + rr + c z,c,n,v,h 1 adiw rdl,k add immediate to word rdh:rdl rdh:rdl + k z,c,n,v,s 2 sub rd, rr subtract two registers rd rd - rr z,c,n,v,h 1 subi rd, k subtract constant from register rd rd - k z,c,n,v,h 1 sbc rd, rr subtract with carry two registers rd rd - rr - c z,c,n,v,h 1 sbci rd, k subtract with carry constant from reg. rd rd - k - c z,c,n,v,h 1 sbiw rdl,k subtract immediate from word rdh:rdl rdh:rdl - k z,c,n,v,s 2 and rd, rr logical and registers rd rd ? rr z,n,v 1 andi rd, k logical and register and constant rd rd ? k z,n,v 1 or rd, rr logical or registers rd rd v rr z,n,v 1 ori rd, k logical or register and constant rd rd v k z,n,v 1 eor rd, rr exclusive or registers rd rd rr z,n,v 1 com rd one?s complement rd 0xff ? rd z,c,n,v 1 neg rd two?s complement rd 0x00 ? rd z,c,n,v,h 1 sbr rd,k set bit(s) in register rd rd v k z,n,v 1 cbr rd,k clear bit(s) in register rd rd ? (0xff - k) z,n,v 1 inc rd increment rd rd + 1 z,n,v 1 dec rd decrement rd rd ? 1 z,n,v 1 tst rd test for zero or minus rd rd ? rd z,n,v 1 clr rd clear register rd rd rd z,n,v 1 ser rd set register rd 0xff none 1 branch instructions rjmp k relative jump pc pc + k + 1 none 2 ijmp indirect jump to (z) pc z none 2 rcall k relative subroutine call pc pc + k + 1 none 3 icall indirect call to (z) pc znone3 ret subroutine return pc stack none 4 reti interrupt return pc stack i 4 cpse rd,rr compare, skip if equal if (rd = rr) pc pc + 2 or 3 none 1/2/3 cp rd,rr compare rd ? rr z, n,v,c,h 1 cpc rd,rr compare with carry rd ? rr ? c z, n,v,c,h 1 cpi rd,k compare register with immediate rd ? k z, n,v,c,h 1 sbrc rr, b skip if bit in register cleared if (rr(b)=0) pc pc + 2 or 3 none 1/2/3 sbrs rr, b skip if bit in register is set if (rr(b)=1) pc pc + 2 or 3 none 1/2/3 sbic p, b skip if bit in i/o register cleared if (p(b)=0) pc pc + 2 or 3 none 1/2/3 sbis p, b skip if bit in i/o register is set if (p(b)=1) pc pc + 2 or 3 none 1/2/3 brbs s, k branch if status flag set if (sreg(s) = 1) then pc pc+k + 1 none 1/2 brbc s, k branch if status flag cleared if (sreg(s) = 0) then pc pc+k + 1 none 1/2 breq k branch if equal if (z = 1) then pc pc + k + 1 none 1/2 brne k branch if not equal if (z = 0) then pc pc + k + 1 none 1/2 brcs k branch if carry set if (c = 1) then pc pc + k + 1 none 1/2 brcc k branch if carry cleared if (c = 0) then pc pc + k + 1 none 1/2 brsh k branch if same or higher if (c = 0) then pc pc + k + 1 none 1/2 brlo k branch if lower if (c = 1) then pc pc + k + 1 none 1/2 brmi k branch if minus if (n = 1) then pc pc + k + 1 none 1/2 brpl k branch if plus if (n = 0) then pc pc + k + 1 none 1/2 brge k branch if greater or equal, signed if (n v= 0) then pc pc + k + 1 none 1/2 brlt k branch if less than zero, signed if (n v= 1) then pc pc + k + 1 none 1/2 brhs k branch if half carry flag set if (h = 1) then pc pc + k + 1 none 1/2 brhc k branch if half carry flag cleared if (h = 0) then pc pc + k + 1 none 1/2 brts k branch if t flag set if (t = 1) then pc pc + k + 1 none 1/2 brtc k branch if t flag cleared if (t = 0) then pc pc + k + 1 none 1/2 brvs k branch if overflow flag is set if (v = 1) then pc pc + k + 1 none 1/2 brvc k branch if overflow flag is cleared if (v = 0) then pc pc + k + 1 none 1/2 brie k branch if interrupt enabled if ( i = 1) then pc pc + k + 1 none 1/2 brid k branch if interrupt disabled if ( i = 0) then pc pc + k + 1 none 1/2 bit and bit-test instructions sbi p,b set bit in i/o register i/o(p,b) 1none2 cbi p,b clear bit in i/o register i/o(p,b) 0none2 lsl rd logical shift left rd(n+1) rd(n), rd(0) 0 z,c,n,v 1 lsr rd logical shift right rd(n) rd(n+1), rd(7) 0 z,c,n,v 1 rol rd rotate left through carry rd(0) c,rd(n+1) rd(n),c rd(7) z,c,n,v 1 ror rd rotate right through carry rd(7) c,rd(n) rd(n+1),c rd(0) z,c,n,v 1 208 2586n?avr?04/11 attiny25/45/85 asr rd arithmetic shift right rd(n) rd(n+1), n=0..6 z,c,n,v 1 swap rd swap nibbles rd(3..0) rd(7..4),rd(7..4) rd(3..0) none 1 bset s flag set sreg(s) 1 sreg(s) 1 bclr s flag clear sreg(s) 0 sreg(s) 1 bst rr, b bit store from register to t t rr(b) t 1 bld rd, b bit load from t to register rd(b) tnone1 sec set carry c 1c1 clc clear carry c 0 c 1 sen set negative flag n 1n1 cln clear negative flag n 0 n 1 sez set zero flag z 1z1 clz clear ze ro flag z 0 z 1 sei global interrupt enable i 1i1 cli global interrupt disable i 0 i 1 ses set signed test flag s 1s1 cls clear signed test flag s 0 s 1 sev set twos complement overflow. v 1v1 clv clear twos complement overflow v 0 v 1 set set t in sreg t 1t1 clt clear t in sreg t 0 t 1 seh set half carry flag in sreg h 1h1 clh clear half carry flag in sreg h 0 h 1 data transfer instructions mov rd, rr move between registers rd rr none 1 movw rd, rr copy register word rd+1:rd rr+1:rr none 1 ldi rd, k load immediate rd knone1 ld rd, x load indirect rd (x) none 2 ld rd, x+ load indirect and post-inc. rd (x), x x + 1 none 2 ld rd, - x load indirect and pre-dec. x x - 1, rd (x) none 2 ld rd, y load indirect rd (y) none 2 ld rd, y+ load indirect and post-inc. rd (y), y y + 1 none 2 ld rd, - y load indirect and pre-dec. y y - 1, rd (y) none 2 ldd rd,y+q load indirect with displacement rd (y + q) none 2 ld rd, z load indirect rd (z) none 2 ld rd, z+ load indirect and post-inc. rd (z), z z+1 none 2 ld rd, -z load indirect and pre-dec. z z - 1, rd (z) none 2 ldd rd, z+q load indirect with displacement rd (z + q) none 2 lds rd, k load direct from sram rd (k) none 2 st x, rr store indirect (x) rr none 2 st x+, rr store indirect and post-inc. (x) rr, x x + 1 none 2 st - x, rr store indirect and pre-dec. x x - 1, (x) rr none 2 st y, rr store indirect (y) rr none 2 st y+, rr store indirect and post-inc. (y) rr, y y + 1 none 2 st - y, rr store indirect and pre-dec. y y - 1, (y) rr none 2 std y+q,rr store indirect with displacement (y + q) rr none 2 st z, rr store indirect (z) rr none 2 st z+, rr store indirect and post-inc. (z) rr, z z + 1 none 2 st -z, rr store indirect and pre-dec. z z - 1, (z) rr none 2 std z+q,rr store indirect with displacement (z + q) rr none 2 sts k, rr store direct to sram (k) rr none 2 lpm load program memory r0 (z) none 3 lpm rd, z load program memory rd (z) none 3 lpm rd, z+ load program memory and post-inc rd (z), z z+1 none 3 spm store program memory (z) r1:r0 none in rd, p in port rd pnone1 out p, rr out port p rr none 1 push rr push register on stack stack rr none 2 pop rd pop register from stack rd stack none 2 mcu control instructions nop no operation none 1 sleep sleep (see specific descr. for sleep function) none 1 wdr watchdog reset (see specific descr. for wdr/timer) none 1 break break for on-chip debug only none n/a mnemonics operands description operation flags #clocks 209 2586n?avr?04/11 attiny25/45/85 25. ordering information notes: 1. for speed vs. supply voltage, see section 21.3 ?speed? on page 168 . 2. all packages are pb-free, halide-free and fully green, and th ey comply with the european directive for restriction of hazard- ous substances (rohs). 3. code indicators: ? h: nipdau lead finish ? u or n: matte tin ? r: tape & reel 4. can also be supplied in wafer form. contact your local atme l sales office for ordering information and minimum quantities. 5. for typical and electrical characteristics for this device please consult appendix a, attiny25/v specification at 105 c. 25.1 attiny25 speed (mhz) (1) supply voltage (v) temperature range package (2) ordering code (3) 10 1.8 ? 5.5 industrial (-40 c to +85 c) (4) 8p3 attiny25v-10pu 8s2 attiny25v-10su attiny25v-10sur attiny25v-10sh s8s1 attiny25v-10ssu attiny25v-10ssur attiny25v-10ssh 20m1 attiny25v-10mu ATTINY25V-10MUR industrial (-40 c to +105 c) (5) 8s2 attiny25v-10sn attiny25v-10snr s8s1 attiny25v-10ssn attiny25v-10ssnr 20 2.7 ? 5.5 industrial (-40 c to +85 c) (4) 8p3 attiny25-20pu 8s2 attiny25-20su attiny25-20sur attiny25-20sh s8s1 attiny25-20ssu attiny25-20ssur attiny25-20ssh 20m1 attiny25-20mu attiny25-20mur industrial (-40 c to +105 c) (5) 8s2 attiny25-20sn attiny25-20snr s8s1 attiny25-20ssn attiny25-20ssnr package types 8p3 8-lead, 0.300" wide, plastic dual inline package (pdip) 8s2 8-lead, 0.208" wide, plastic gull -wing small outline (eiaj soic) s8s1 8-lead, 0.150" wide, plastic gull -wing small outli ne (jedec soic) 20m1 20-pad, 4 x 4 x 0.8 mm body, quad flat no-lead/micro lead frame package (qfn/mlf) 210 2586n?avr?04/11 attiny25/45/85 notes: 1. for speed vs. supply voltage, see section 21.3 ?speed? on page 168 . 2. all packages are pb-free, halide-free and fully green and they comply with the european directive for restriction of hazard- ous substances (rohs). 3. code indicators: ? h: nipdau lead finish ? u: matte tin ? r: tape & reel 4. these devices can also be supplied in wafer form. please contact your local atmel sales office for detailed ordering informa- tion and minimum quantities. 25.2 attiny45 speed (mhz) (1) supply voltage (v) temperature range package (2) ordering code (3) 10 1.8 ? 5.5 industrial (-40 c to +85 c) (4) 8p3 attiny45v-10pu 8s2 attiny45v-10su attiny45v-10sur attiny45v-10sh 8x attiny45v-10xu attiny45v-10xur 20m1 attiny45v-10mu attiny45v-10mur 20 2.7 ? 5.5 industrial (-40 c to +85 c) (4) 8p3 attiny45-20pu 8s2 attiny45-20su attiny45-20sur attiny45-20sh 8x attiny45-20xu attiny45-20xur 20m1 attiny45-20mu attiny45-20mur package types 8p3 8-lead, 0.300" wide, plastic dual inline package (pdip) 8s2 8-lead, 0.208" wide, plastic gull -wing small outline (eiaj soic) 8x 8-lead, 4.4 mm wide, plastic thin shrink small outline package (tssop) 20m1 20-pad, 4 x 4 x 0.8 mm body, quad flat no-lead/micro lead frame package (qfn/mlf) 211 2586n?avr?04/11 attiny25/45/85 notes: 1. for speed vs. supply voltage, see section 21.3 ?speed? on page 168 . 2. all packages are pb-free, halide-free and fully green and they comply with the european directive for restriction of hazard- ous substances (rohs). 3. code indicators: ? h: nipdau lead finish ? u: matte tin ? r: tape & reel 4. these devices can also be supplied in wafer form. please contact your local atmel sales office for detailed ordering informa- tion and minimum quantities. 25.3 attiny85 speed (mhz) (1) supply voltage (v) temperature range package (2) ordering code (3) 10 1.8 ? 5.5 industrial (-40 c to +85 c) (4) 8p3 attiny85v-10pu 8s2 attiny85v-10su attiny85v-10sur attiny85v-10sh 20m1 attiny85v-10mu attiny85v-10mur 20 2.7 ? 5.5 industrial (-40 c to +85 c) (4) 8p3 attiny85-20pu 8s2 attiny85-20su attiny85-20sur attiny85-20sh 20m1 attiny85-20mu attiny85-20mur package types 8p3 8-lead, 0.300" wide, plastic dual inline package (pdip) 8s2 8-lead, 0.208" wide, plastic gull -wing small outline (eiaj soic) 20m1 20-pad, 4 x 4 x 0.8 mm body, quad flat no-lead/micro lead frame package (qfn/mlf) 212 2586n?avr?04/11 attiny25/45/85 26. packaging information 26.1 8p3 2325 orchard parkway san jose, ca 95131 title drawing no. r rev. 8p3 , 8-lead, 0.300" wide body, plastic dual in-line package (pdip) 01/09/02 8p3 b d d1 e e1 e l b2 b a2 a 1 n ea c b3 4 plcs top view side view end view common dimensions (unit of measure = inches) symbol min nom max note notes: 1. this drawing is for general information only; refer to jedec drawing ms-001, variation ba for additional information. 2. dimensions a and l are measured with the package seated in jedec seating plane gauge gs-3. 3. d, d1 and e1 dimensions do not include mold flash or protrusions. mold flash or protrusions shall not exceed 0.010 inch. 4. e and ea measured with the leads constrained to be perpendicular to datum. 5. pointed or rounded lead tips are preferred to ease insertion. 6. b2 and b3 maximum dimensions do not include dambar protrusions. dambar protrusions shall not exceed 0.010 (0.25 mm). a 0.210 2 a2 0.115 0.130 0.195 b 0.014 0.018 0.022 5 b2 0.045 0.060 0.070 6 b3 0.030 0.039 0.045 6 c 0.008 0.010 0.014 d 0.355 0.365 0.400 3 d1 0.005 3 e 0.300 0.310 0.325 4 e1 0.240 0.250 0.280 3 e 0.100 bsc ea 0.300 bsc 4 l 0.115 0.130 0.150 2 213 2586n?avr?04/11 attiny25/45/85 26.2 8s2 title drawing no. gpc rev. packa g e drawin g contact: p a ck a gedr a wing s @ a tmel.com 8s 2 s tn f 8s 2, 8 -le a d, 0.20 8? body, pl as tic s m a ll o u tline p a ck a ge (eiaj) 4/15/0 8 common dimen s ion s (unit of me asu re = mm) s ymbol min nom max note note s : 1. thi s dr a wing i s for gener a l inform a tion only; refer to eiaj dr a wing edr-7 3 20 for a ddition a l inform a tion. 2. mi s m a tch of the u pper a nd lower die s a nd re s in bu rr s a ren't incl u ded. 3 . determine s the tr u e geometric po s ition. 4. v a l u e s b ,c a pply to pl a ted termin a l. the s t a nd a rd thickne ss of the pl a ting l a yer s h a ll me asu re b etween 0.007 to .021 mm. a 1.70 2.16 a1 0.05 0.25 b 0. 3 5 0.4 8 4 c 0.15 0. 3 5 4 d 5.1 3 5. 3 5 e1 5.1 8 5.40 2 e 7.70 8 .26 l 0.51 0. 8 5 0 8 e 1.27 b s c 3 1 1 n n e e top view t o p v i e w c c e1 e 1 end view e n d v i e w a a b b l l a1 a 1 e e d d s ide view s i d e v i e w 214 2586n?avr?04/11 attiny25/45/85 26.3 s8s1 2 3 25 orch a rd p a rkw a y sa n jo s e, ca 951 3 1 title drawing no. r rev. s8s 1 , 8 -le a d, 0.150" wide body, pl as tic g u ll wing s m a ll o u tline (jedec s oic) 7/2 8 /0 3 s8s 1 a common dimen s ion s (unit of me asu re = mm) s ymbol min nom max note note s :1. thi s dr a wing i s for gener a l inform a tion only; refer to jedec dr a wing m s -012 for proper dimen s ion s , toler a nce s , d a t u m s ,e tc. e 5.79 6.20 e1 3 . 8 1 3 .99 a1. 3 5 1.75 a1 0.1 0.25 d4. 8 0 4.9 8 c 0.17 0.25 b 0. 3 1 0.51 l 0.4 1.27 e 1.27 b s c 0 o 8 o top view s ide view end view 1 n c a a1 b l e d e1 e 215 2586n?avr?04/11 attiny25/45/85 26.4 8x title drawing no. r rev. note: the s e dr a wing s a re for gener a l inform a tion only. refer to jedec dr a wing mo-15 3 ac. 2 3 25 orch a rd p a rkw a y sa n jo s e, ca 951 3 1 4/14/05 8 x , 8 -le a d, 4.4 mm body width, pl as tic thin s hrink s m a ll o u tline p a ck a ge (t ss op) 8 xa common dimen s ion s (unit of me asu re = mm) s ymbol min nom max note a 1.05 1.10 1.20 a1 0.05 0.10 0.15 b 0.25 ? 0. 3 0 c ? 0.127 ? d 2.90 3 .05 3 .10 e1 4. 3 0 4.40 4.50 e 6.20 6.40 6.60 e 0.65 typ l 0.50 0.60 0.70 ? 0 o ? 8 o c c a a b b l l a1 a 1 d s ide view top view end view e e 1 1 e1 e 1 e ? ? 216 2586n?avr?04/11 attiny25/45/85 26.5 20m1 2325 orchard parkway san jose, ca 95131 title drawing no. r rev. 20m1 , 20-pad, 4 x 4 x 0.8 mm body, lead pitch 0.50 mm, a 20m1 10/27/04 2.6 mm exposed pad, micro lead frame package (mlf) a 0.70 0.75 0.80 a1 ? 0.01 0.05 a2 0.20 ref b 0.18 0.23 0.30 d 4.00 bsc d2 2.45 2.60 2.75 e 4.00 bsc e2 2.45 2.60 2.75 e 0.50 bsc l 0.35 0.40 0.55 side view pin 1 id pin #1 notch (0.20 r) bottom view top view note: reference jedec standard mo-220, fig . 1 (saw singulation) wggd-5. common dimensions (unit of measure = mm) symbol min nom max note d e e a2 a1 a d2 e2 0.08 c l 1 2 3 b 1 2 3 217 2586n?avr?04/11 attiny25/45/85 27. errata 27.1 errata attiny25 the revision letter in this section refers to the revision of the attiny25 device. 27.1.1 rev d and e no known errata. 27.1.2 rev b and c ? eeprom read may fail at low supply voltage / low clock frequency 1. eeprom read may fail at low supp ly voltage / low clock frequency trying to read eeprom at low clock frequencies and/or low supply voltage may result in invalid data. problem fix/workaround do not use the eeprom when cl ock frequency is below 1mhz and supply voltage is below 2v. if operating frequency can not be raised above 1mhz then supply voltage should be more than 2v. similarly, if supply voltage can not be raised above 2v then operating fre- quency should be more than 1mhz. this feature is known to be temperature dependent but it has not been characterised. guidelines are given for room temperature, only. 27.1.3 rev a not sampled. 27.2 errata attiny45 the revision letter in this section refers to the revision of the attiny45 device. 27.2.1 rev f and g no known errata 27.2.2 rev d and e ? eeprom read may fail at low supply voltage / low clock frequency 1. eeprom read may fail at low supp ly voltage / low clock frequency trying to read eeprom at low clock frequencies and/or low supply voltage may result in invalid data. problem fix/workaround do not use the eeprom when cl ock frequency is below 1mhz and supply voltage is below 2v. if operating frequency can not be raised above 1mhz then supply voltage should be more than 2v. similarly, if supply voltage can not be raised above 2v then operating fre- quency should be more than 1mhz. this feature is known to be temperature dependent but it has not been characterised. guidelines are given for room temperature, only. 218 2586n?avr?04/11 attiny25/45/85 27.2.3 rev b and c ? pll not locking ? eeprom read from applicat ion code does not work in lock bit mode 3 ? eeprom read may fail at low supply voltage / low clock frequency ? timer counter 1 pwm output generation on oc1b- xoc1b does not work correctly 1. pll not locking when at frequencies below 6. 0 mhz, the pll will not lock problem fix / workaround when using the pll, run at 6.0 mhz or higher. 2. eeprom read from applic ation code does not work in lock bit mode 3 when the memory lock bits lb2 and lb1 are programmed to mode 3, eeprom read does not work from the application code. problem fix/work around do not set lock bit protection mode 3 when the application code needs to read from eeprom. 3. eeprom read may fail at low supp ly voltage / low clock frequency trying to read eeprom at low clock frequencies and/or low supply voltage may result in invalid data. problem fix/workaround do not use the eeprom when cl ock frequency is below 1mhz and supply voltage is below 2v. if operating frequency can not be raised above 1mhz then supply voltage should be more than 2v. similarly, if supply voltage can not be raised above 2v then operating fre- quency should be more than 1mhz. this feature is known to be temperature dependent but it has not been characterised. guidelines are given for room temperature, only. 4. timer counter 1 pwm output generation on oc1b ? xoc1b does not work correctly timer counter1 pwm output oc1b-xoc1b does no t work correctly. only in the case when the control bits, com1b1 and com1b0 are in the same mode as com1a1 and com1a0, respectively, the oc1b-xoc1b output works correctly. problem fix/work around the only workaround is to use same control setting on com1a[1:0] and com1b[1:0] control bits, see table 14-4 in the data sheet. the problem has been fixed for tiny45 rev d. 27.2.4 rev a ? too high power down power consumption ? debugwire looses communication when single stepping into interrupts ? pll not locking ? eeprom read from applicat ion code does not work in lock bit mode 3 ? eeprom read may fail at low supply voltage / low clock frequency 1. too high power down power consumption three situations will lead to a too high power down power consumption. these are: ? an external clock is selected by fuses, bu t the i/o port is still enabled as an output. 219 2586n?avr?04/11 attiny25/45/85 ? the eeprom is read before entering power down. ? vcc is 4.5 volts or higher. problem fix / workaround ? when using external clock, avoid setting the clock pin as output. ? do not read the eeprom if power do wn power consumption is important. ? use vcc lower than 4.5 volts. 2. debugwire looses communication when single stepping into interrupts when receiving an inte rrupt during single st epping, debugwire will loose communication. problem fix / workaround ? when singlestepping, disable interrupts. ? when debugging interrupts, use breakpoints within the interrupt routine, and run into the interrupt. 3. pll not locking when at frequencies below 6. 0 mhz, the pll will not lock problem fix / workaround when using the pll, run at 6.0 mhz or higher. 4. eeprom read from applic ation code does not work in lock bit mode 3 when the memory lock bits lb2 and lb1 are programmed to mode 3, eeprom read does not work from the application code. problem fix/work around do not set lock bit protection mode 3 when the application code needs to read from eeprom. 5. eeprom read may fail at low supp ly voltage / low clock frequency trying to read eeprom at low clock frequencies and/or low supply voltage may result in invalid data. problem fix/workaround do not use the eeprom when cl ock frequency is below 1mhz and supply voltage is below 2v. if operating frequency can not be raised above 1mhz then supply voltage should be more than 2v. similarly, if supply voltage can not be raised above 2v then operating fre- quency should be more than 1mhz. this feature is known to be temperature dependent but it has not been characterised. guidelines are given for room temperature, only. 220 2586n?avr?04/11 attiny25/45/85 27.3 errata attiny85 the revision letter in this section refers to the revision of the attiny85 device. 27.3.1 rev b and c no known errata. 27.3.2 rev a ? eeprom read may fail at low supply voltage / low clock frequency 1. eeprom read may fail at low supp ly voltage / low clock frequency trying to read eeprom at low clock frequencies and/or low supply voltage may result in invalid data. problem fix/workaround do not use the eeprom when cl ock frequency is below 1mhz and supply voltage is below 2v. if operating frequency can not be raised above 1mhz then supply voltage should be more than 2v. similarly, if supply voltage can not be raised above 2v then operating fre- quency should be more than 1mhz. this feature is known to be temperature dependent but it has not been characterised. guidelines are given for room temperature, only. 221 2586n?avr?04/11 attiny25/45/85 28. datasheet revision history 28.1 rev. 2586n-04/11 1. added: ? section ?capacitive touch sensing? on page 6 . 2. updated: ? document template. ? removed ?preliminary? on front page. all devices now final and in production. ? section ?limitations? on page 37 . ? program example on page 51 . ? section ?overview? on page 126 . ? table 17-4 on page 139 . ? section ?limitations of debugwire? on page 144 . ? section ?serial programming algorithm? on page 156 . ? table 21-7 on page 171 . ? eeprom errata on pages 217 , 217 , 218 , 219 , and 220 ? ordering information on pages 209 , 210 , and 211 . 28.2 rev. 2586m-07/10 1. clarified section 6.4 ?clock output buffer? on page 32 . 2. added ordering codes -sn and -snr for attiny25 extended temperature. 28.3 rev. 2586l-06/10 1. added: ? tssop for attiny45 in ?features? on page 1 , pinout figure 1-1 on page 2 , ordering information in section 25.2 ?attiny45? on page 210 , and packaging information in section 26.4 ?8x? on page 215 ? table 6-11, ?capacitance of low-freq uency crystal oscillator,? on page 29 ? figure 22-36 on page 196 and figure 22-37 on page 196 , typical characteristics plots for bandgap voltage vs. v cc and temperature ? extended temperature in section 25.1 ?attiny25? on page 209 , ordering information ? tape & reel part numbers in ordering information, in section 25.1 ?attiny25? on page 209 and section 25.2 ?attiny45? on page 210 2. updated: ? ?features? on page 1 , removed preliminary from attiny25 ? section 8.4.2 ?code example? on page 46 ? ?pcmsk ? pin change mask register? on page 54 , bit descriptions ? ?tccr1 ? timer/counter1 control register? on page 92 and ?gtccr ? general timer/counter1 control register? on page 93 , com bit descriptions clarified ? section 20.3.2 ?calibration bytes? on page 154 , frequencies (8 mhz, 6.4 mhz) ? table 20-11, ?minimum wait delay before writing the next flash or eeprom location,? on page 157 , value for t wd_erase 222 2586n?avr?04/11 attiny25/45/85 ? table 20-16, ?high-voltage serial programming instruction set for attiny25/45/85,? on page 163 ? table 21-1, ?dc characteristics. t a = -40 c to +85 c,? on page 166 , notes adjusted ? table 21-11, ?serial programming characteristics, t a = -40 c to +85 c, v cc = 1.8 - 5.5v (unless otherwise noted),? on page 175 , added t sliv ? bit syntax throughout the datasheet, e.g. from cs02:0 to cs0[2:0]. 28.4 rev. 2586k-01/08 1. updated document template. 2. added sections: ? ?data retention? on page 6 ? ?low level interrupt? on page 51 ? ?device signature imprint table? on page 153 3. updated sections: ? ?internal pll for fast peripheral clock generation - clkpck? on page 24 ? ?system clock and clock options? on page 23 ? ?internal pll in attiny15 compatibility mode? on page 24 ? ?sleep modes? on page 35 ? ?software bod disable? on page 36 ? ?external interrupts? on page 51 ? ?timer/counter1 in pwm mode? on page 101 ? ?usi ? universal serial interface? on page 111 ? ?temperature measurement? on page 137 ? ?reading lock, fuse and signature data from software? on page 147 ? ?program and data memory lock bits? on page 151 ? ?fuse bytes? on page 152 ? ?signature bytes? on page 154 ? ?calibration bytes? on page 154 ? ?system and reset characteristics? on page 170 4. added figures: ? ?reset pin output voltage vs. sink current (v cc = 3v)? on page 189 ? ?reset pin output voltage vs. sink current (v cc = 5v)? on page 190 ? ?reset pin output voltage vs. source current (v cc = 3v)? on page 190 ? ?reset pin output voltage vs. source current (v cc = 5v)? on page 191 5. updated figure: ? ?reset logic? on page 41 6. updated tables: ? ?start-up times for internal calibrat ed rc oscillator clock? on page 28 ? ?start-up times for internal calibrated rc osc illator clock (in attiny15 mode)? on page 28 ? ?start-up times for the 128 khz internal oscillator? on page 29 ? ?compare mode select in pwm mode? on page 89 223 2586n?avr?04/11 attiny25/45/85 ? ?compare mode select in pwm mode? on page 101 ? ?dc characteristics. t a = -40 c to +85 c? on page 166 ? ?calibration accuracy of intern al rc oscillator? on page 169 ? ?adc characteristics? on page 172 7. updated code example in section: ? ?write? on page 17 8. updated bit descriptions in: ? ?mcucr ? mcu control register? on page 38 ? ?bits 7:6 ? com0a[1:0]: compare match output a mode? on page 80 ? ?bits 5:4 ? com0b[1:0]: compare match output b mode? on page 80 ? ?bits 2:0 ? adts[2:0]: adc auto trigger source? on page 142 ? ?spmcsr ? store program memory control and status register? on page 149 . 9. updated descript ion of feature ?eeprom read may fa il at low supply voltage / low clock frequency? in sections: ? ?errata attiny25? on page 217 ? ?errata attiny45? on page 217 ? ?errata attiny85? on page 220 10. updated package description in sections: ? ?attiny25? on page 209 ? ?attiny45? on page 210 ? ?attiny85? on page 211 11. updated package drawing: ? ?s8s1? on page 214 12. updated order codes for: ? ?attiny25? on page 209 28.5 rev. 2586j-12/06 1. updated ?low power consumption? on page 1 . 2. updated description of instruction length in ?architectural overview? . 3. updated flash size in ?in-system re-programmable flash program memory? on page 15 . 4. updated cross-references in sections ?atomic byte programming? , ?erase? and ?write? , starting on page 17 . 5. updated ?atomic byte programming? on page 17 . 6. updated ?internal pll for fast peripheral clock generation - clkpck? on page 24 . 7. replaced single clocking system figure with two: figure 6-2 and figure 6-3 . 8. updated table 6-1 on page 25 , table 6-13 on page 30 and table 6-6 on page 28 . 9. updated ?calibrated internal oscillator? on page 27 . 10. updated table 6-5 on page 27 . 11. updated ?osccal ? oscillator calibrati on register? on page 32 . 12. updated ?clkpr ? clock prescale register? on page 33 . 13. updated ?power-down mode? on page 36 . 224 2586n?avr?04/11 attiny25/45/85 28.6 rev. 2586i-09/06 14. updated ?bit 0? in ?prr ? power reduction register? on page 39 . 15. added footnote to table 8-3 on page 48 . 16. updated table 10-5 on page 65 . 17. deleted ?bits 7, 2? in ?mcucr ? mcu control register? on page 66 . 18. updated and moved section ?timer/counter0 prescaler and clock sources?, now located on page 68 . 19. updated ?timer/counter1 initialization for asynchronous mode? on page 89 . 20. updated bit description in ?pllcsr ? pll control and status register? on page 97 and ?pllcsr ? pll control and status register? on page 107 . 21. added recommended maximum frequency in ?prescaling and conversion timing? on page 129 . 22. updated figure 17-8 on page 133 . 23. updated ?temperature measurement? on page 137 . 24. updated table 17-3 on page 138 . 25. updated bit r/w descriptions in: ?timsk ? timer/counter interrupt mask register? on page 84 , ?tifr ? timer/counter interrupt flag register? on page 84 , ?timsk ? timer/counter interrupt mask register? on page 95 , ?tifr ? timer/counter interrupt flag register? on page 96 , ?pllcsr ? pll control and status register? on page 97 , ?timsk ? timer/counter interrupt mask register? on page 106 , ?tifr ? timer/counter interrupt flag register? on page 106 , ?pllcsr ? pll control and status register? on page 107 and ?didr0 ? digital input disable register 0? on page 142 . 26. added limitation to ?limitations of debugwire? on page 144 . 27. updated ?dc characteristics? on page 166 . 28. updated table 21-7 on page 171 . 29. updated figure 21-6 on page 176 . 30. updated table 21-12 on page 176 . 31. updated table 22-1 on page 182 . 32. updated table 22-2 on page 182 . 33. updated table 22-30 , table 22-31 and table 22-32 , starting on page 193 . 34. updated table 22-33 , table 22-34 and table 22-35 , starting on page 194 . 35. updated table 22-39 on page 197 . 36. updated table 22-46 , table 22-47 , table 22-48 and table 22-49 . 1. all characterization data moved to ?electrical characteristics? on page 166 . 2. all register descriptions are gathered up in seperate sections in the end of each chapter. 3. updated table 11-3 on page 81 , table 11-5 on page 82 , table 11-6 on page 83 and table 20-4 on page 152 . 4. updated ?calibrated internal oscillator? on page 27 . 5. updated note in table 7-1 on page 35 . 6. updated ?system control and reset? on page 41 . 7. updated register description in ?i/o ports? on page 55 . 225 2586n?avr?04/11 attiny25/45/85 28.7 rev. 2586h-06/06 28.8 rev. 2586g-05/06 28.9 rev. 2586f-04/06 28.10 rev. 2586e-03/06 8. updated features in ?usi ? universal serial interface? on page 111 . 9. updated code example in ?spi master operation example? on page 113 and ?spi slave operation example? on page 114 . 10. updated ?analog comparator multiplexed input? on page 123 . 11. updated figure 17-1 on page 127 . 12. updated ?signature bytes? on page 154 . 13. updated ?electrical characteristics? on page 166 . 1. updated ?calibrated internal oscillator? on page 27 . 2. updated table 6.5.1 on page 32 . 3. added table 21-2 on page 169 . 1. updated ?internal pll for fast peripheral clock generation - clkpck? on page 24 . 2. updated ?default clock source? on page 31 . 3. updated ?low-frequency crystal oscillator? on page 29 . 4. updated ?calibrated internal oscillator? on page 27 . 5. updated ?clock output buffer? on page 32 . 6. updated ?power management and sleep modes? on page 35 . 7. added ?software bod disable? on page 36 . 8. updated figure 16-1 on page 123 . 9. updated ?bit 6 ? acbg: analog comparator bandgap select? on page 124 . 10. added note for table 17-2 on page 129 . 11. updated ?register summary? on page 205 . 1. updated ?digital input enable and sleep modes? on page 59 . 2. updated table 20-16 on page 163 . 3. updated ?ordering information? on page 209 . 1. updated features in ?analog to digital converter? on page 126 . 2. updated operation in ?analog to digital converter? on page 126 . 3. updated table 17-2 on page 138 . 4. updated table 17-3 on page 138 . 5. updated ?errata? on page 217 . 226 2586n?avr?04/11 attiny25/45/85 28.11 rev. 2586d-02/06 28.12 rev. 2586c-06/05 28.13 rev. 2586b-05/05 28.14 rev. 2586a-02/05 initial revision. 1. updated table 6-13 on page 30 , table 6-10 on page 29 , table 6-3 on page 26 , table 6-9 on page 29 , table 6-5 on page 27 , table 9-1 on page 50 , table 17-4 on page 139 , table 20-16 on page 163 , table 21-8 on page 172 . 2. updated ?timer/counter1 in pwm mode? on page 89 . 3. updated text ?bit 2 ? tov1: timer/counter1 overflow flag? on page 96 . 4. updated values in ?dc characteristics? on page 166 . 5. updated ?register summary? on page 205 . 6. updated ?ordering information? on page 209 . 7. updated rev b and c in ?errata attiny45? on page 217 . 8. all references to power-save mode are removed. 9. updated register adresses. 1. updated ?features? on page 1 . 2. updated figure 1-1 on page 2 . 3. updated code examples on page 18 and page 19 . 4. moved ?temperature measurement? to section 17.12 page 137 . 5. updated ?register summary? on page 205 . 6. updated ?ordering information? on page 209 . 1. clki added, instance s of eemwe/eewe renamed eempe/eepe, removed some tbd. removed ?preliminary description? from ?temperature measurement? on page 137 . 2. updated ?features? on page 1 . 3. updated figure 1-1 on page 2 and figure 8-1 on page 41 . 4. updated table 7-2 on page 39 , table 10-4 on page 65 , table 10-5 on page 65 5. updated ?serial programming instruction set? on page 157 . 6. updated sph register in ?instruction set summary? on page 207 . 7. updated ?dc characteristics? on page 166 . 8. updated ?ordering information? on page 209 . 9. updated ?errata? on page 217 . i 2586n?avr?04/11 attiny25/45/85 table of contents features ................ ................ .............. ............... .............. .............. ............ 1 1 pin configurations ..... ................ ................. ................ ................. ............ 2 1.1 pin descriptions .................................................................................................2 2 overview ............ ................ ................ ............... .............. .............. ............ 4 2.1 block diagram ...................................................................................................4 3 about ............. ................ ................. ................ ................. .............. ............ 6 3.1 resources .........................................................................................................6 3.2 code examples .................................................................................................6 3.3 capacitive touch sensing .................................................................................6 3.4 data retention ...................................................................................................6 4 avr cpu core ................. ................ ................. .............. .............. ............ 7 4.1 introduction ........................................................................................................7 4.2 architectural overview .......................................................................................7 4.3 alu ? arithmetic logic unit ...............................................................................8 4.4 status register ..................................................................................................8 4.5 general purpose register file ........................................................................10 4.6 stack pointer ...................................................................................................11 4.7 instruction execution timing ...........................................................................12 4.8 reset and interrupt handling ...........................................................................12 5 avr memories .......... ................ ................ ................. ................ ............. 15 5.1 in-system re-programmable flash program memory ....................................15 5.2 sram data memory ........................................................................................15 5.3 eeprom data memory . ................. ................ ............. ............ ............. ..........16 5.4 i/o memory ......................................................................................................20 5.5 register description ........................................................................................20 6 system clock and clock options ................ ................. .............. .......... 23 6.1 clock systems and their distribution ...............................................................23 6.2 clock sources .................................................................................................25 6.3 system clock prescaler ..................................................................................31 6.4 clock output buffer .........................................................................................32 6.5 register description ........................................................................................32 7 power management and sleep mo des ............... .............. ............ ........ 35 ii 2586n?avr?04/11 attiny25/45/85 7.1 sleep modes ....................................................................................................35 7.2 software bod disable .....................................................................................36 7.3 power reduction register ...............................................................................37 7.4 minimizing power consumption ......................................................................37 7.5 register description ........................................................................................38 8 system control and reset ...... ................ ................. ................ ............. 41 8.1 resetting the avr ...........................................................................................41 8.2 reset sources .................................................................................................41 8.3 internal voltage reference ..............................................................................44 8.4 watchdog timer ..............................................................................................44 8.5 register description ........................................................................................46 9 interrupts ........ ................. ................ ................. .............. .............. .......... 50 9.1 interrupt vectors in attiny25/45/85 .................................................................50 9.2 external interrupts ...........................................................................................51 9.3 register description ........................................................................................53 10 i/o ports ............... ................ .............. ............... .............. .............. .......... 55 10.1 introduction ......................................................................................................55 10.2 ports as general digital i/o .............................................................................56 10.3 alternate port functions ..................................................................................59 10.4 register description ........................................................................................66 11 8-bit timer/counter0 with pw m .............. ................. ................ ............. 67 11.1 features ..........................................................................................................67 11.2 overview ..........................................................................................................67 11.3 timer/counter0 prescaler and clock sources ................................................68 11.4 counter unit ....................................................................................................70 11.5 output compare unit .......................................................................................71 11.6 compare match output unit ............................................................................72 11.7 modes of operation .........................................................................................73 11.8 timer/counter timing diagrams .....................................................................78 11.9 register description ........................................................................................80 12 8-bit timer/counter1 .. ................ ................. ................ ................. .......... 86 12.1 timer/counter1 prescaler ...............................................................................86 12.2 counter and compare units ............................................................................86 12.3 register description ........................................................................................92 iii 2586n?avr?04/11 attiny25/45/85 13 8-bit timer/counter1 in at tiny15 mode ......... .............. .............. .......... 98 13.1 timer/counter1 prescaler ...............................................................................98 13.2 counter and compare units ............................................................................98 13.3 register description ......................................................................................103 14 dead time generator ........ .............. .............. .............. .............. ........... 108 14.1 register description ......................................................................................109 15 usi ? universal seri al interface ............ ................. ................ ............. 111 15.1 features ........................................................................................................111 15.2 overview ........................................................................................................111 15.3 functional descriptions .................................................................................112 15.4 alternative usi usage ...................................................................................117 15.5 register descriptions ....................................................................................118 16 analog comparator .......... .............. .............. .............. .............. ........... 123 16.1 analog comparator multiplexed input ...........................................................123 16.2 register description ......................................................................................124 17 analog to digital converter ............. ............... .............. .............. ........ 126 17.1 features ........................................................................................................126 17.2 overview ........................................................................................................126 17.3 operation .......................................................................................................127 17.4 starting a conversion ....................................................................................128 17.5 prescaling and conversion timing ................................................................129 17.6 changing channel or reference selection ...................................................132 17.7 adc noise canceler .....................................................................................132 17.8 analog input circuitry ....................................................................................133 17.9 noise canceling techniques .........................................................................134 17.10 adc accuracy definitions .............................................................................134 17.11 adc conversion result .................................................................................136 17.12 temperature measurement ...........................................................................137 17.13 register description ......................................................................................138 18 debugwire on-chip debug s ystem .............. .............. .............. ........ 143 18.1 features ........................................................................................................143 18.2 overview ........................................................................................................143 18.3 physical interface ..........................................................................................143 18.4 software break points ...................................................................................144 iv 2586n?avr?04/11 attiny25/45/85 18.5 limitations of debugwire .............................................................................144 18.6 register description ......................................................................................144 19 self-programming the flash .. ............... ................. ................ ............. 145 19.1 performing page erase by spm ....................................................................145 19.2 filling the temporary buffer (page loading) .................................................145 19.3 performing a page write ...............................................................................146 19.4 addressing the flash during self-programming ...........................................146 19.5 eeprom write prevents writing to spmcsr ............. ............ ............. ........147 19.6 reading lock, fuse and signature data from software ...............................147 19.7 preventing flash corruption ..........................................................................149 19.8 programming time for flash when using spm ............................................149 19.9 register description ......................................................................................149 20 memory programming ........ .............. ............... .............. .............. ........ 151 20.1 program and data memory lock bits ...........................................................151 20.2 fuse bytes .....................................................................................................152 20.3 device signature imprint table .....................................................................153 20.4 page size ......................................................................................................154 20.5 serial downloading ........................................................................................155 20.6 high-voltage serial programming ..................................................................159 20.7 high-voltage serial programming algorithm .................................................159 21 electrical characteristics ... .............. ............... .............. .............. ........ 166 21.1 absolute maximum ratings* .........................................................................166 21.2 dc characteristics .........................................................................................166 21.3 speed ............................................................................................................168 21.4 clock characteristics .....................................................................................169 21.5 system and reset characteristics ................................................................170 21.6 brown-out detection .....................................................................................171 21.7 adc characteristics ......................................................................................172 21.8 serial programming characteristics ..............................................................175 21.9 high-voltage serial programming characteristics .........................................176 22 typical characteristics ....... .............. ............... .............. .............. ........ 177 22.1 active supply current ....................................................................................177 22.2 idle supply current ........................................................................................180 22.3 supply current of i/o modules ......................................................................182 22.4 power-down supply current ..........................................................................183 v 2586n?avr?04/11 attiny25/45/85 22.5 pin pull-up .....................................................................................................184 22.6 pin driver strength ........................................................................................187 22.7 pin threshold and hysteresis ........................................................................191 22.8 bod threshold ..............................................................................................194 22.9 internal oscillator speed .................... ...........................................................197 22.10 current consumption of peripheral units ......................................................201 22.11 current consumption in reset and reset pulsewidth ..................................203 23 register summary ............ .............. .............. .............. .............. ........... 205 24 instruction set summary ... .............. ............... .............. .............. ........ 207 25 ordering information .......... .............. ............... .............. .............. ........ 209 25.1 attiny25 ........................................................................................................209 25.2 attiny45 ........................................................................................................210 25.3 attiny85 ........................................................................................................211 26 packaging information .......... ................ ................. ................ ............. 212 26.1 8p3 ................................................................................................................212 26.2 8s2 ................................................................................................................213 26.3 s8s1 ..............................................................................................................214 26.4 8x ..................................................................................................................215 26.5 20m1 ..............................................................................................................216 27 errata ........... ................ ................ ................. ................ .............. ........... 217 27.1 errata attiny25 ..............................................................................................217 27.2 errata attiny45 ..............................................................................................217 27.3 errata attiny85 ..............................................................................................220 28 datasheet revision history .. ................ ................. ................ ............. 221 28.1 rev. 2586n-04/11 .........................................................................................221 28.2 rev. 2586m-07/10 .........................................................................................221 28.3 rev. 2586l-06/10 ..........................................................................................221 28.4 rev. 2586k-01/08 ..........................................................................................222 28.5 rev. 2586j-12/06 ..........................................................................................223 28.6 rev. 2586i-09/06 ...........................................................................................224 28.7 rev. 2586h-06/06 .........................................................................................225 28.8 rev. 2586g-05/06 .........................................................................................225 28.9 rev. 2586f-04/06 ..........................................................................................225 28.10 rev. 2586e-03/06 ..........................................................................................225 vi 2586n?avr?04/11 attiny25/45/85 28.11 rev. 2586d-02/06 .........................................................................................226 28.12 rev. 2586c-06/05 .........................................................................................226 28.13 rev. 2586b-05/05 ..........................................................................................226 28.14 rev. 2586a-02/05 ..........................................................................................226 vii 2586n?avr?04/11 attiny25/45/85 2586n?avr?04/11 headquarters international atmel corporation 2325 orchard parkway san jose, ca 95131 usa tel: (+1)(408) 441-0311 fax: (+1)(408) 487-2600 atmel asia limited unit 01-5 & 16, 19f bea tower, millennium city 5 418 kwun tong road kwun tong, kowloon hong kong tel: (+852) 2245-6100 fax: (+852) 2722-1369 atmel munich gmbh business campus parkring 4 d-85748 garching b. munich germany tel: (+49) 89-31970-0 fax: (+49) 89-3194621 atmel japan 9f, tonetsu shinkawa bldg. 1-24-8 shinkawa chuo-ku, tokyo 104-0033 japan tel: (+81)(3) 3523-3551 fax: (+81)(3) 3523-7581 product contact web site www.atmel.com technical support avr@atmel.com sales contact www.atmel.com/contacts literature requests www.atmel.com/literature disclaimer: the information in this document is provided in connection with atmel products. no license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of atmel products. except as set forth in atmel?s terms and condi- tions of sale located on atmel?s web site, atmel assumes no li ability whatsoever and disclaims any express, implied or statutor y warranty relating to its products including, but not limited to, the implied warranty of merchantability, fitness for a particu lar purpose, or non-infringement. in no event shall atmel be liable for any direct, indirect, consequential, punitive, special or i nciden- tal damages (including, without limitation, damages for loss of profits, business interruption, or loss of information) arising out of the use or inability to use this document, even if atme l has been advised of the possibility of such damages. atmel makes no representations or warranties with respect to the accuracy or comp leteness of the contents of this document and reserves the rig ht to make changes to specifications and product descriptions at any time without notice. atmel does not make any commitment to update the information contained her ein. unless specifically provided otherwise, atmel products are not suitable for, and shall not be used in, automotive applications. atmel?s products are not int ended, authorized, or warranted for use as components in applications in tended to support or sustain life. ? 2011 atmel corporation. all rights reserved. atmel ? , logo and combinations thereof, and others ar e registered trademarks or trademarks of at mel corporation or its subsidiaries. o ther terms and product names may be trademarks of others. |
Price & Availability of ATTINY25V-10MUR
 |
|
|
|
|
All Rights Reserved © IC-ON-LINE 2003 - 2022 |
| [Add Bookmark] [Contact Us] [Link exchange] [Privacy policy] |
|
Mirror Sites : [www.datasheet.hk]
[www.maxim4u.com] [www.ic-on-line.cn]
[www.ic-on-line.com] [www.ic-on-line.net]
[www.alldatasheet.com.cn]
[www.gdcy.com]
[www.gdcy.net] |